Method for performing radio link monitoring

ABSTRACT

A method for performing radio link monitoring comprises performing, by a user equipment (UE), a radio link monitoring (RLM) procedure with first RLM parameters; receiving, at the UE, a message including at least one second RLM parameter; identifying, by the UE, a difference between the first RLM parameters and the at least one second RLM parameter; and resetting, at the UE, at least one of the first RLM parameters in response to identifying the difference between the first RLM parameters and the at least one second RLM parameter. The method may configure the UE upon performing RLM by adapting the difference between the current RLM parameters and the future parameters, so that the UE behavior may become clear.

This application is a 371 of International Application No.PCT/IB2018/059021, filed Nov. 16, 2018, which claims the benefit of U.S.Application No. 62/587,218, filed Nov. 16, 2017, the disclosures ofwhich are fully incorporated herein by reference.

TECHNICAL FIELD

Particular embodiments relate to the field of reconfiguring a userequipment (UE); and more specifically, to methods, apparatus and systemsfor reconfiguring the UE upon the UE performing a radio link monitoring(RLM).

BACKGROUND

In new radio (NR) which is also referred as 5G or Next Generation, NRarchitecture is being discussed in 3GPP and the current concept isillustrated in FIG. 1, where eNB denotes LTE eNodeB, gNB and ng-eNB orevolved eNB, denote NR base stations (BSs) where one NR BS maycorrespond to one or more transmission/reception points, and the linesbetween the nodes illustrate the corresponding interfaces which areunder discussion in 3GPP. Further, FIG. 2 illustrates deploymentscenarios with NR BS which are discussed in 3GPP.

Multi-antenna schemes for NR are currently being discussed in 3GPP. ForNR, frequency ranges up to 100 GHz are considered. High-frequency radiocommunication above 6 GHz suffers from significant path loss andpenetration loss. Therefore, massive MIMO schemes for NR are considered.

With massive MIMO, three approaches to beamforming have been discussed:analog, digital, hybrid, and a combination of the two. An examplediagram for hybrid beamforming is shown in FIG. 3. Beamforming may be ontransmission beams and/or reception beams, network side or UE side.

FIGS. 4a and 4b illustrate example beam sweeping with two subarrays andthree subarrays respectively. Regarding beam sweeping, the analog beamof a subarray may be steered toward a single direction on each OFDMsymbol, and hence the number of subarrays determines the number of beamdirections and the corresponding coverage on each OFDM symbol. However,the number of beams to cover the whole serving area is typically largerthan the number of subarrays, especially when the individual beam-widthis narrow. Therefore, to cover the whole serving area, multipletransmissions with narrow beams differently steered in time domain arealso likely to be needed. The provision of multiple narrow coveragebeams for this purpose has been called “beam sweeping”. For analog andhybrid beamforming, the beam sweeping seems to be essential to providethe basic coverage in NR. For this purpose, multiple OFDM symbols, inwhich differently steered beams can be transmitted through subarrays,may be assigned and periodically transmitted.

FIG. 5 illustrates an example configuration of SS blocks, SS bursts andSS burst sets/series. FIG. 5 describes a non-limiting example ifsynchronization signal (SS) block and SS burst configuration which maybe assumed in other embodiments. The signals comprised in SS block maybe used for measurements on NR carrier, including intra-frequency,inter-frequency, and inter-RAT which is NR measurements from anotherRAT. SS block may also be referred to as SS/physical broadcast channel(PBCH) block or SS block (SSB).

NR-primary synchronization signal (PSS), NR-secondary synchronizationsignal (SSS) and/or NR-PBCH may be transmitted within an SS block. For agiven frequency band, an SS block corresponds to a number of N OFDMsymbols based on one subcarrier spacing which is a default orconfigured, and N is a constant. UE may be able to identify at leastOFDM symbol index, slot index in a radio frame and radio frame numberfrom an SS block. A single set of possible SS block time locations withrespect to radio frame or with respect to SS burst set is specified perfrequency band. At least for multi-beams case, at least the time indexof SS-block is indicated to the UE. The position(s) of actualtransmitted SS-blocks may be informed for helping CONNECTED/IDLE modemeasurement, for helping CONNECTED mode UE to receive DL data/control inunused SS-blocks and potentially for helping IDLE mode UE to receive DLdata/control in unused SS-blocks. For different frequency ranges, themaximum number, L, of SS-blocks within SS burst set is 4 for frequencyrange up to 3 GHz, 8 for frequency range from 3 GHz to 6 GHz, or 64 forfrequency range from 6 GHz to 52.6 GHz.

Regarding SS burst set, one or multiple SS burst(s) further compose anSS burst set or series where the number of SS bursts within a SS burstset is finite. From physical layer specification perspective, at leastone periodicity of SS burst set is supported. From UE perspective, SSburst set transmission is periodic. At least for initial cell selection,UE may assume a default periodicity of SS burst set transmission for agiven carrier frequency, for example, one of 5 ms, 10 ms, 20 ms, 40 ms,80 ms, or 160 ms. UE may assume that a given SS block is repeated with aSS burst set periodicity. By default, the UE may neither assume the gNBtransmits the same number of physical beam(s), nor the same physicalbeam(s) across different SS-blocks within an SS burst set. In a specialcase, an SS burst set may comprise one SS burst.

For each carrier, the SS blocks may be time-aligned or overlap fully orat least in part, or the beginning of the SS blocks may be time-alignedwhen the actual number of transmitted SS blocks is different indifferent cells.

FIG. 6 illustrates an example mapping for SS blocks within a time slotand within a 5 ms window. All SS blocks within a burst set are withinthe 5 ms window, but the number of SS blocks within such window dependson the numerology, for example, up to 64 SS blocks with 240 kHzsubcarrier spacing.

The purpose of radio link monitoring (RLM) is to monitor the radio linkquality of the serving cell of the UE and use that information to decidewhether the UE is in in-sync or out-of-sync with respect to that servingcell. In LTE, RLM is carried out by UE performing measurement ondownlink reference symbols (CRS) in RRC_CONNECTED state. If results ofradio link monitoring indicate number of consecutive out of sync (OOS)indications, then the UE starts RLF procedure and declares radio linkfailure (RLF) after the expiry of RLF time (e.g. T310). The actualprocedure is carried out by comparing the estimated downlink referencesymbol measurements to some target BLER, Q_(out) and Q_(in). Q_(out) andQ_(in) correspond to block error rate (BLER) of hypothetical physicaldownlink control channel (PDCCH)/physical control format indicatorchannel (PCIFCH) transmissions from the serving cell. Examples ofQ_(out) and Q_(in) are 10% and 2% respectively.

FIG. 7 illustrates an example radio link failure in LTE. The current RLFprocedure in LTE has two phases, as depicted in FIG. 7. The first phasestarts upon radio problem detection and leads to radio link failuredetection. The second phase which is a RRC recovery phase starts uponradio link failure detection or handover failure and leads to RRC_IDLEin case the RRC recovery fails.

For single carrier and carrier aggregation (CA), re-establishment istriggered when PCell experiences RLF. The UE does not monitor the RLF ofSCells, which are monitored by the eNB.

For Dual Connectivity (DC), the first phase of the radio link failureprocedure is supported for PCell and PSCell. Re-establishment istriggered when PCell experiences RLF. However, upon detecting RLF on thePSCell, the re-establishment procedure is not triggered at the end ofthe first phase. Instead, the UE informs the radio link failure ofPSCell to the MeNB.

RLF may be triggered by layer 1 (L1, a.k.a. physical layer or PHY) orlayer 2 (L2), which is then reported to layer 3 (L3). RLM is responsiblefor L1-triggering, upon receiving N310 consecutive “out-of-sync”indications from lower layers and no recovery which is no “in-sync”.L2-triggering may be, e.g., upon indication from RLC that the maximumnumber of retransmissions has been reached or upon random access problemindication from MAC.

TABLE 1 RLF-related timers in LTE Timer Start Stop At expiry T310 Upondetecting Upon receiving N311 If security is not activated: NOTE1physical layer consecutive in-sync go to RRC_IDLE else: NOTE2 problemsfor the indications from lower initiate the connection re- PCell i.e.upon layers for the PCell, upon establishment procedure receiving N310triggering the handover consecutive out-of- procedure and upon syncindications initiating the connection from lower layers re-establishmentprocedure T311 Upon initiating the Selection of a suitable E- EnterRRC_IDLE NOTE1 RRC connection re- UTRA cell or a cell usingestablishment another RAT. procedure T312 Upon triggering a Uponreceiving N311 If security is not activated: NOTE2 measurement reportconsecutive in-sync go to RRC_IDLE else: for a measurement indicationsfrom lower initiate the connection re- identity for which layers, upontriggering the establishment procedure T312 has been handover procedure,upon configured, while initiating the connection T310 is runningre-establishment procedure, and upon the expiry of T310 T313 Upondetecting Upon receiving N314 Inform E-UTRAN about NOTE2 physical layerconsecutive in-sync the SCG radio link failure problems for theindications from lower by initiating the SCG PSCell i.e. upon layers forthe PSCell, upon failure information receiving N313 initiating theconnection procedure as specified in consecutive out-of-re-establishment 5.6.13. sync indications procedure, upon SCG from lowerlayers release and upon receiving RRCConnectionReconfiguration includingMobilityControlInfoSCG

Regarding RLF handling in NR, while the RLM functionality hadsignificant changes in NR, in other words, a more configurable procedurehas been defined where the network may define the RS type, exactresources to be monitored and even the BLER for IS and OOS indications,RLF did not have major changes in NR compared to LTE. In RAN2, thefollowing has been agreed in RAN2 #99-bis, in Prague:

Agreements 1 RLF detection will be specified for NR in the RRC spec (asin LTE) 2 For Dec. 17, RLF will be based on the periodic IS/OOSindications from L1 (i.e. this is same frame work as LTE)

RLF was discussed for NR in RAN2 #97-bis in Spokane, and the followinghas been agreed:

Agreements 1: For connected mode, UE declares REF upon timer expiry dueto DL OOS detection, random access procedure failure detection, and RLCfailure detection. FFS whether maximum ARQ retransmission is onlycriteria for RLC failure (needs to be discussed in common UP/CPsession). 2 In NR RLM procedure, physical layer performs out of sync/insync indication and RRC declares RLF. 3 For RLF purposes, RAN2preference is that the in sync/out of sync indication should be a percell indication, and we aim for a single procedure for both multi-beamand single beam operation.

Then in RAN2 #99, in Berlin, the following has been agreed:

Agreements 1 RAN2 understanding of RAN 1 agreements that at least PHYinforms RRC of periodic out-of-sync/in-sync indications. 2 Baselinebehaviour when there are no indications from lower layers related tobeam failure/recovery: i/RRC detects DL radio link problem ifconsecutive N1 number of periodic out-of-sync indications are received.ii/RRC stops the timer if consecutive N2 number of periodic in-syncindications are received while the timer runs.

In other words, as in LTE, it may assume that RLF in NR will also begoverned by any one of the following parameter or equivalent selectedfrom counters, N310, N311, N313, N314, and timers, 310, T311, T301,T313, T314.

Hence, it may expect similar behavior as in LTE to certain extent. Belowit reproduces how RLF variables may be configured in NR and UE behavior,recently agreed for NR.

Regarding radio link failure related actions, in response to detectingphysical layer problems in RRC_CONNECTED, the UE shall:

-   -   1> upon receiving N310 consecutive “out-of-sync” indications for        the PCell from lower layers while T311 is not running:        -   2> start timer T310;    -   1> upon receiving N313 consecutive “out-of-sync” indications for        the PSCell from lower layers while T307 is not running:        -   2> start T313;            FFS: Under which condition physical layer problems detection            is performed, e.g. neither T300, T301, T304 nor T311 is            running. It's subject to the harmonization of the RRC            procedures for RRC Connection            establishment/resume/re-establishment and RRC connection            reconfiguration.            FFS: The naming of the timers.

Regarding a recovery of physical layer problems, upon receiving N311consecutive “in-sync” indications for the PCell from lower layers whileT310 is running, the UE shall:

-   -   1> stop timer T310;        FFS: whether to support T312 for early RLF declaration in NR.    -   NOTE 1: In this case, the UE maintains the RRC connection        without explicit signalling, i.e. the UE maintains the entire        radio resource configuration.    -   NOTE 2: Periods in time where neither “in-sync” nor        “out-of-sync” is reported by layer 1 do not affect the        evaluation of the number of consecutive “in-sync” or        “out-of-sync” indications.

Upon receiving N314 consecutive “in-sync” indications for the PSCellfrom lower layers while T313 is running, the UE shall:

-   -   1> stop timer T313.

Upon detecting a radio link failure, the UE shall:

-   -   1> upon T310 expiry; or    -   1> upon random access problem indication from MCG MAC while T311        is not running; or        FFS: Under which condition physical layer problems detection is        performed, e.g. neither T300, T301, T304 nor T311 is running.        It's subject to the harmonization of the RRC procedures for RRC        Connection establishment/resume/re-establishment and RRC        connection reconfiguration.    -   1> upon indication from MCG RLC that the maximum number of        retransmissions has been reached for an SRB or for an MCG or        split DRB:        FFS whether maximum ARQ retransmission is only criteria for RLC        failure.    -   2> consider radio link failure to be detected for the MCG i.e.        RLF;        FFS Whether indications related to beam failure recovery may        affect the declaration of RLF.        FFS: How to handle RLC failure in CA duplication for MCG DRB and        SRB.        FFS: RLF related measurement reports e.g VarRLF-Report is        supported in NR.    -   2> if AS security has not been activated:        -   3> perform the actions upon leaving RRC_CONNECTED as            specified in x.x.x, with release cause ‘other’;    -   2> else:        -   3> initiate the connection re-establishment procedure as            specified in x.x.x;

Otherwise, the UE shall:

-   -   1> upon T313 expiry; or    -   1> upon random access problem indication from SCG MAC; or    -   1> upon indication from SCG RLC that the maximum number of        retransmissions has been reached for an SCG SRB, SCG or split        DRB:        -   2> consider radio link failure to be detected for the SCG            i.e. SCG-RLF;            FFS: How to handle RLC failure in CA duplication for SCG DRB            and SRB.    -   2> initiate the SCG failure information procedure as specified        in 5.6.4 to report SCG radio link failure.

Table 2 below illustrates timers related to radio link failure.

TABLE 2 RLF-related timers in NR Timer Start Stop At expiry T307Reception of Successful completion of Inform E-UTRAN/NRRRCConnectionReconfiguration random access on the about the SCG changemessage including PSCell, upon initiating re- failure by initiating theMobilityControlInfo establishment and upon SCG failure information SCGSCG release procedure as specified in 5.6.4. T310 Upon detecting Uponreceiving N311 If security is not activated: physical layer consecutivein-sync go to RRC_IDLE else: problems for the indications from lowerinitiate the connection re- PCell i.e. upon layers for the PCell, uponestablishment procedure receiving N310 triggering the handoverconsecutive out-of- procedure and upon sync indications initiating theconnection from lower layers re-establishment procedure T311 Uponinitiating the Selection of a suitable NR Enter RRC_IDLE RRC connectionre- cell or a cell using another establishment RAT. procedure T313 Upondetecting Upon receiving N314 Inform E-UTRAN/NR physical layerconsecutive in-sync about the SCG radio link problems for theindications from lower failure by initiating the PSCell i.e. upon layersfor the PSCell, upon SCG failure information receiving N313 initiatingthe connection procedure as specified in consecutive out-of-re-establishment 5.6.4. sync indications procedure, upon SCG from lowerlayers release and upon receiving RRCConnectionReconfiguration includingMobilityControlInfoSCG

Table 3 below illustrates constants related to radio link failure.

TABLE 3 RLF-related constants Constant Usage N310 Maximum number ofconsecutive “out-of-sync” indications for the PCell received from lowerlayers N311 Maximum number of consecutive “in-sync” indications for thePCell received from lower layers N313 Maximum number of consecutive“out-of-sync” indications for the PSCell received from lower layers N314Maximum number of consecutive “in-sync” indications for the PSCellreceived from lower layers

The IE RLF-TimersAndConstants contains UE specific timers and constantsapplicable for UEs in RRC_CONNECTED.

RLF-TimersAndConstants information element -- ASN1STARTRLF-TimersAndConstants::= CHOICE {  release  NULL,  setup  SEQUENCE {  t301  ENUMERATED {   ms100, ms200, ms300, ms400, ms600,  ms1000,ms1500,   ms2000, ms2500, ms3000, ms3500,   ms4000, ms5000,  t310    ms6000, ms8000, ms10000},  ENUMERATED {   ms0, ms50, ms100,ms200, ms500,   ms1000, ms2000, ms4000, ms6000},   n310  ENUMERATED {  n1, n2, n3, n4, n6, n8, n10, n20},   t311  ENUMERATED {   ms1000,ms3000, ms5000, ms10000,   ms15000, ms20000, ms30000},   n311 ENUMERATED {   n1, n2, n3, n4, n5, n6, n8, n10},   . . .  } }   t313 ENUMERATED {   ms0, ms50, ms100, ms200, ms500,   ms1000, ms2000},  n313  ENUMERATED {   n1, n2, n3, n4, n6, n8, n10, n20},   n314 ENUMERATED {   n1, n2 n3, n4, n5 n6 n8, n10},   . . .  } } -- ASN1STOP

RLM is typically performed in LTE by the UE estimating a metric, such assignal to noise and interference ratio (SINR) on reference symbols, suchas cell specific reference symbols (CRS). The quality metric (e.g. SINR)is not standardized but rather PDCCH block error (BLER) thresholds forout of sync (Q_(out)) and in-sync (Q_(in)), such as 10% and 2%, arespecified. The UE is expected to estimate BLER for a so calledhypothetical PDCCH BLER using its quality measurement (e.g. SINR), suchthat it detects out of sync when the BLER is greater than Q_(out), anddetects in sync when the BLER is smaller than Q_(in). The BLER isreferred to as hypothetical BLER because it can be estimated by the UEfrom RS, even when there are no PDCCH transmissions targeted to the UE.Since it would be undesirable to send an out-of-sync or an in-syncindication in response to short term fading of the radio channel, socalled evaluation periods are specified for Q_(in) and Q_(out)evaluation. The evaluation periods are fixed in the specifications andare performed by layer 1 in addition to the configurable timers andcounters for the higher layers mentioned in the table above.

Regarding RLM in NR, one of the main differences in the NR RLMfunctionality, compared to LTE, is that the RLM functionality in LTE isdescribed in the specifications, so that the UE actions do not depend onparameters configured by the network. On the other hand, in NR, due tothe wide range of frequencies and diversity of envisioned deploymentsand services, RLM is a quite configurable procedure. In NR, the networkmay configure the UE to perform RLM based on different RS types (SS/PBCHblock and CSI-RS), the exact resources to be monitored and the exactnumber to generate IS/OOS indications, and the BLER thresholds, so thatmeasured SINR values may be mapped to them to generate IS/OOS events tobe indicated to the higher layers.

RLM in NR is performed based on up to 8 preliminary RLM RS resourcesconfigured by the network, where one RLM-RS resource may be either oneSS/PBCH block or one CSI-RS resource/port, or where the RLM-RS resourcesare UE-specifically configured at least in case of CSI-RS based RLM.

When a UE is configured to perform RLM on one or multiple RLM-RSresource(s), periodic IS (in-sync) is indicated if the estimated linkquality corresponding to hypothetical PDCCH BLER based on at least Y=1RLM-RS resource among all configured X RLM-RS resource(s) is aboveQ_(in) threshold, and periodic OOS is indicated if the estimated linkquality corresponding to hypothetical PDCCH BLER based on all configuredX RLM-RS resource(s) is below Q_(out) threshold.

The same problem applies to the cell quality derivation for support ofRRC_CONNECTED state mobility, i.e. handover, as the cell qualityderivation mechanism is similar. The consequence is that measurementreports for N>1 would be triggered earlier, if triggered by the cellqualities of cells with fewer beams compared to the case of cells withmore beams, which is also counterproductive and may result in suboptimalhandover decisions.

As RLM in NR is a configurable procedure, the network may configure theUE with different parameters affecting how the UE generates IS and OOSindications to the higher layers e.g. via an RRCConfiguration message.RLM parameters may be provided when the UE establishes a connection(e.g. moving from RRC_IDLE to RRC_CONNECTED state), when the UE resumesan RRC connection (e.g. moving from RRC_INACTIVE to RRC_CONNECTEDstate), when the UE performs handover to a target cell, when upon beamfailure detection, the UE performs beam recovery, or when the networkdecides to re-configure previously provided parameters for other reasonssuch as when the configuration of the control channels the UE needs tomonitor is changed.

Upon the configuration or re-configuration of RLM parameters, the UEbehavior is unclear and currently unspecified regarding what the UEshall do upon the configuration or re-configuration of the set of RLM RSresources to be monitored, or upon the configuration or re-configurationof the BLER threshold pair for generating IS and OOS indications to thehigher layers. In certain scenarios, the set of RLM RS resources beingchanged means that one or more new RLM RSs are added, one or more areremoved, or one or more are changed or replaced by other, when networkadds or removes RLM RS resources without changing the RS type, e.g.CSI-RS or SS/PBCH block remains the same, or when network adds orremoves RLM RS resources that may be from a different RS type, e.g. UEis monitoring only a set of CSI-RS resources and network adds SS/PBCHblock and removes a set of the CSI-RS resources or vice-versa.

SUMMARY

To address the foregoing problems with existing solutions, disclosed aremethods, a user equipment (UE), and a communication system forperforming radio link monitoring upon configuring a UE by identifying adifference between the current RLM parameter which the UE is performingand the future RLM parameter which the UE is going to adapt. The presentdisclosure implements a solution for configuring the UE with the futureRLM parameter upon the UE performing the current RLM parameter.Therefore, the UE behavior is clear during the configuration orre-configuration.

Several embodiments are elaborated in this disclosure. According to oneembodiment, a method for performing radio link monitoring comprisesperforming, by a UE, a RLM procedure with first RLM parameters. Themethod additionally comprises receiving, at the UE, a message includingat least one second RLM parameter. The method further comprisesidentifying, by the UE, a difference between the first RLM parametersand the second RLM parameter. The method yet further comprisesresetting, at the UE, at least one of the first RLM parameters inresponse to identifying the difference between the first RLM parametersand the second RLM parameter.

In one embodiment, the first RLM parameters and the second RLM parameterare RLM reference signal (RLM-RS) resources for in sync and out of syncindications, block error rate (BLER) for in-sync and out-of-syncindications, or a combination of RLM-RS resources and BLER for in-syncand out-of-sync indications.

In one embodiment, identifying the difference between the first RLMparameters and the second RLM parameter comprises identifying that thefirst RLM parameters are a first group of RLM-RS resources, andidentifying that the second RLM parameter is a second group of RLM-RSresources added to the first group of RLM-RS resources. In oneembodiment, the method further comprises adapting the first group of theRLM-RS resources and the added second group of RLM-RS resources.

In one embodiment, identifying the difference between the first RLMparameters and the second RLM parameter comprises identifying that thefirst RLM parameters are a first group of RLM-RS resources, andidentifying that the second RLM parameter is a second group of RLM-RSresources that replace a subset of the first group of RLM-RS resources.In one embodiment, the method further comprises adapting thepartly-replaced first group of the RLM-RS resources and the replacingsecond group of RLM-RS resources.

In one embodiment, identifying the difference between the first RLMparameters and the second RLM parameter comprises identifying that thefirst RLM parameters are a first group of RLM-RS resources, andidentifying that the second RLM parameter is a second group of RLM-RSresources comprising the first group of RLM-RS resources without asubset of RLM-RS resources. In one embodiment, the method furthercomprises adapting the first group of RLM-RS resources without thesubset of RLM-RS resources.

In one embodiment, identifying the difference between the first RLMparameters and the second RLM parameter comprises identifying that thefirst RLM parameters are a first group of RLM-RS resources, andidentifying that the second RLM parameter is a second group of RLM-RSresources which replace the first group of RLM-RS resources. In oneembodiment, the method further comprises adapting the second group ofRLM-RS resources.

In one embodiment, identifying the difference between the first RLMparameters and the second RLM parameter comprises identifying that theat least one second RLM parameter increases a BLER threshold to generatethe out-of-sync indications. In one embodiment, resetting at least oneof the first RLM parameters comprises resetting at least one out-of-synccounter in response to identifying the difference between the first RLMparameters and the second RLM parameter.

In one embodiment, identifying the difference between the first RLMparameters and the at least one second RLM parameter comprisesidentifying that the at least one second RLM parameter decreases a BLERthreshold to generate the out-of-sync indications. In one embodiment,resetting at least one of the first RLM parameters comprises resettingat least one out-of-sync counter in response to identifying thedifference between the first RLM parameters and the second RLMparameter.

In one embodiment, identifying the difference between the first RLMparameters and the at least one second RLM parameter comprisesidentifying that the at least one second RLM parameter increases a BLERthreshold to generate the in-sync indications. In one embodiment,resetting at least one of the first RLM parameters comprises resettingat least one in-sync counter in response to identifying the differencebetween the first RLM parameters and the second RLM parameter.

In one embodiment, identifying the difference between the first RLMparameters and the at least one second RLM parameter comprisesidentifying that the at least one second RLM parameter decreases a BLERthreshold to generate the in-sync indications. In one embodiment,resetting at least one of the first RLM parameters comprises resettingat least one in-sync counter in response to identifying the differencebetween the first RLM parameters and the second RLM parameter.

In one embodiment, when the first group of RLM-RS resources is not thesame type of RLM-RS resources as the second group of RLM-RS resources,the UE does not reset any timers or counters.

In one embodiment, when the first group of RLM-RS resources is the sametype of RLM-RS resources as the second group of RLM-RS resources, the UEresets at least one timer or counter.

In one embodiment, the method further comprises stopping at least oneradio link failure (RLF) related timer at the UE.

According to another embodiment, a UE for performing radio linkmonitoring comprises at least one processor, and at least one storagethat stores processor-executable instructions, when executed by theprocessor, causes the UE to perform a radio link monitoring (RLM)procedure with first RLM parameters; receive, from a network node, amessage including at least one second RLM parameter; identify adifference between the first RLM parameters and the at least one secondRLM parameter; and reset at least one of the first RLM parameters inresponse to identifying the difference between the first RLM parametersand the at least one second RLM parameter.

According to another embodiment, a communication system for performingradio link monitoring comprises a UE and a network node. The UEcomprises at least one processor configured to perform a radio linkmonitoring (RLM) procedure with first RLM parameters; receive, from anetwork node, a message including at least one second RLM parameter;identify a difference between the first RLM parameters and the at leastone second RLM parameter; and reset at least one of the first RLMparameters in response to identifying the difference between the firstRLM parameters and the at least one second RLM parameter.

Certain aspects of the present disclosure and their embodiments mayprovide solutions to these or other challenges. There are, proposedherein, various embodiments which address one or more of the issuesdisclosed herein.

Certain embodiments may provide one or more of the following technicaladvantages. The methods disclosed in the present disclosure may identifythe difference between the current configuration and the futureconfiguration for a UE, so that the UE may properly be configured whileperforming radio link monitoring.

The present embodiments further an optimized UE behavior in radio linkmonitoring when the network configures a UE. The present embodimentsfacilitate the configuration procedure and improve the networkefficiency since UE does not need to reset or stop the currentconfiguration to adapt the future configuration. The UE may reset onlypart of the RLM parameters in the current configuration to adapt thefuture configuration.

Various other features and advantages will become obvious to one ofordinary skill in the art in light of the following detailed descriptionand drawings. Certain embodiments may have none, some, or all of therecited advantages.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawing figures incorporated in and forming a part ofthis specification illustrate several aspects of the disclosure, andtogether with the description serve to explain the principles of thedisclosure.

FIG. 1 illustrates an example new radio architecture;

FIG. 2 illustrates multiple example new radio deployments;

FIG. 3 illustrates an example hybrid beamforming;

FIGS. 4a and 4b illustrate example beam sweepings with two subarrays andthree subarrays;

FIG. 5 illustrates an example configuration of SS blocks, SS bursts, andSS burst sets;

FIG. 6 illustrates example mappings for different numbers of SS blocks;

FIG. 7 illustrates an example radio link failure in LTE;

FIG. 8 illustrates an example transition period upon changingconfiguration of RLM-RS, according to certain embodiments;

FIG. 9 illustrates an example wireless network, according to certainembodiments;

FIG. 10 illustrates an example user equipment, according to certainembodiments;

FIG. 11 illustrates an example virtualization environment, according tocertain embodiments;

FIG. 12 illustrates an example telecommunication network connected viaan intermediate network to a host computer, according to certainembodiments;

FIG. 13 illustrates an example host computer communicating via a basestation with a user equipment over a partially wireless connection,according to certain embodiments;

FIG. 14 illustrates an example method implemented in a communicationsystem including a host computer, a base station and a user equipment,according to certain embodiments;

FIG. 15 illustrates another example method implemented in acommunication system including a host computer, a base station and auser equipment, according to certain embodiments;

FIG. 16 illustrates another further example method implemented in acommunication system including a host computer, a base station and auser equipment, according to certain embodiments;

FIG. 17 illustrates another yet example method implemented in acommunication system including a host computer, a base station and auser equipment, according to certain embodiments;

FIG. 18 illustrates a flow diagram of an example method in a userequipment, in accordance with certain embodiments; and

FIG. 19 illustrates a block schematic of an example user equipment, inaccordance with certain embodiments.

DETAILED DESCRIPTION

As radio link monitoring is a configurable procedure, the UE behaviorbecomes unclear, and the actions which the UE should be performing uponthe configuration are not specified. Not knowing the UE behavior uponconfiguration may cause certain problems, such as how the UE willgenerate indications to higher layers. Therefore, particular embodimentsof the present disclosure propose a method to identify a differencebetween the current RLM parameters and the future RLM parameters, sothat the UE may be configured with the future RLM parameters by adaptingthe difference while using the current RLM parameters.

With the identification of the difference between the current RLMparameters and the future RLM parameters, the UE behavior may becomedefinite upon the configuration. Before adapting the future RLMparameters, the UE may keep performing the current RLM parameters.Furthermore, the UE may only reset or partially stop current RLMparameters to adapt the future RLM parameters. This solution enables anefficient way to perform radio link monitoring steadily upon configuringthe future RLM parameters at the UE.

Some of the embodiments contemplated herein will now be described morefully with reference to the accompanying drawings. Other embodiments,however, are contained within the scope of the subject matter disclosedherein, the disclosed subject matter should not be construed as limitedto only the embodiments set forth herein; rather, these embodiments areprovided by way of example to convey the scope of the subject matter tothose skilled in the art.

Generally, all terms used herein are to be interpreted according totheir ordinary meaning in the relevant technical field, unless adifferent meaning is clearly given and/or is implied from the context inwhich it is used. All references to a/an/the element, apparatus,component, means, step, etc. are to be interpreted openly as referringto at least one instance of the element, apparatus, component, means,step, etc., unless explicitly stated otherwise. The steps of any methodsdisclosed herein do not have to be performed in the exact orderdisclosed, unless a step is explicitly described as following orpreceding another step and/or where it is implicit that a step mustfollow or precede another step. Any feature of any of the embodimentsdisclosed herein may be applied to any other embodiment, whereverappropriate. Likewise, any advantage of any of the embodiments may applyto any other embodiments, and vice versa. Other objectives, features andadvantages of the enclosed embodiments will be apparent from thefollowing description.

In some embodiments a non-limiting term “UE” is used. The UE herein canbe any type of wireless device capable of communicating with networknode or another UE over radio signals. The UE may also be radiocommunication device, target device, device to device (D2D) UE, machinetype UE or UE capable of machine to machine communication (M2M), asensor equipped with UE, iPAD, Tablet, mobile terminals, smart phone,laptop embedded equipped (LEE), laptop mounted equipment (LME), USBdongles, Customer Premises Equipment (CPE) etc.

Also, in some embodiments, generic terminology “network node” is used.It can be any kind of network node which may comprise of a radio networknode such as base station, radio base station, base transceiver station,base station controller, network controller, multi-standard radio BS,gNB, NR BS, evolved Node B (eNB), Node B, Multi-cell/multicastCoordination Entity (MCE), relay node, access point, radio access point,Remote Radio Unit (RRU) Remote Radio Head (RRH), a multi-standard BS(a.k.a. MSR BS), a core network node (e.g., MME, SON node, acoordinating node, positioning node, MDT node, etc.), or even anexternal node (e.g., 3rd party node, a node external to the currentnetwork), etc. The network node may also comprise a test equipment.

Furthermore, in some embodiments, the term “base station (BS)” maycomprise, e.g., gNB, en-gNB or ng-eNB or a relay node, or any BScompliant with the embodiments. The term “radio node” used herein may beused to denote a UE or a radio network node. The term “signaling” usedherein may comprise any of high-layer signaling (e.g., via RRC or alike), lower-layer signaling (e.g., via a physical control channel or abroadcast channel), or a combination thereof. The signaling may beimplicit or explicit. The signaling may further be unicast, multicast orbroadcast. The signaling may also be directly to another node or via athird node.

In some embodiments, the term “RLM procedure” used herein may refer toany process occurs, or action taken by the UE during the RLM. Examplesof such processes or actions are OOS evaluation, IS evaluation,filtering of IS/OOS (e.g. start of counters), triggering of RLF, startor expiration of RLF timer etc.

In some embodiments, the term “RLM performance” used herein may refer toany criteria or metric which characterizes the performance of the RLMperformed by a radio node. Examples of RLM performance criteria areevaluation period over which the IS/OOS are detected, time period withinwhich the UE transmitter is to be turned off upon expiration of RLFtimer etc.

The term numerology here may comprise any one or a combination of:subcarrier spacing, number of subcarriers within a bandwidth, resourceblock size, symbol length, control plane (CP) length, etc. In onespecific non-limiting example, numerology comprises subcarrier spacingof 7.5 kHz, 15 kHz, 30 kHz, 60 kHz, 120 kHz, or 240 kHz. In anotherexample, numerology is the CP length which may be used with subcarrierspacing 30 kHz or larger.

In an example method performed in a UE, the present disclosure firstlyaddresses details about configuration/re-configuration of referencesignal (RS) type. In the following embodiments, the term “RLM procedure”refers to both the procedure where the UE generates IS and OOSindications from measurements (L1 procedure) and the procedure where theUE uses these indications to increments the counters to start and stopthe RLF timers. Hence, within the present disclosure, the term “RLMprocedure” refers to both the L1 RLM procedure and the RLF procedureexecuted in RRC layer.

According to one embodiment, upon reconfiguring RLM parameters after theUE has already been configured to perform RLM, the UE can be triggeredto perform the RLM either according to a first RLM mode (RLM1) oraccording to a second RLM mode (RLM2). In certain embodiments, the RLMparameters may be RLM-RS, BLER pair to generate IS/OOS indications, orboth the RLM-RS and the BLER pair.

According to the first mode, RLM1, the UE may restart the RLM procedure.For example, the UE may abandon the ongoing RLM procedure by resettingall the RLM associated parameters, such as IS/OOS counters by settingthese counters to zero, stopping or re-setting the RLF related timers,removing estimated DL quality measurements or removing estimatedhistoric samples for IS/OOS evaluations and measurement performed basedon the previously configured resources, etc. In certain embodiments, theIS/OOS counters may be N310, N311, N313 or N314. In certain embodiments,the RLF related timers may be T310, T311, or T313.

According to the second mode, RLM2, the UE may continue the ongoing RLMprocedure. The UE may further be configured with the informationregarding how the existing parameter values may be continued. Forexample, the UE may continue the ongoing RLM procedure without resettingall the RLM associated parameters, such as counters, timers, estimatedDL quality, or estimated historic samples for IS/OOS evaluations etc. Incertain embodiments, the counters may be N310, N311, N313 or N314. Incertain embodiments, the timers may be T310, T311, or T313. The UE maybe configured to reset or initialize only subset of the RLM associatedparameters. For example, only reset RLF timer T310 but not RLM countersor vice versa. The details are provided for different cases, such as thecases in standard sections 5.2.1-5.2.3.

The UE may be triggered to perform the RLM according to RLM1 or RLM2based on a pre-defined rule and/or based on information received from anetwork node. The received information may comprise a configurationmessage or an indication. In certain embodiments, the indication may beone of the pre-defined identifiers corresponding to the mode. Examplesof configuration messages may be RRC signaling, MAC command, or Layer-1message. In certain embodiments, the configuration messages may be sentover downlink (DL) control channel via downlink control information(DCI). The DL control channel may be PDCCH.

The UE may adapt a RLM procedure, depending on the type of change inRLM-RS. In one embodiment, the rule whether the UE may trigger RLM1 orRLM2 upon change in RLM-RS is dependent upon the type of reconfigurationof the RLM-RS. Examples of types of reconfiguration of the RLM-RS are anaddition of one or more new RLM-RS; a replacement of one or moreexisting RLM-RS by new RLM-RS; a removal of one or more existing RLM-RS;and a complete replacement of all existing RLM-RS by new RLM-RS.

The UE behavior adaptation whether to apply RLM1 or RLM2 upon RLM-RSreconfiguration is described herein by means of examples below.

In the first scenario of one or more RLM RS resources being added to theset of RLM-RS resources, the size of the set of the RLM RS resourcesincreases. The UE is currently configured with RLM-RS (RLM-RS1), and theUE is further configured with a new set of RLM-RS (e.g. RLM-RS2) fordoing the RLM. The combined set of RLM-RS (RLM-RS3) comprising RLM-RS1and RLM-RS2 is then used by the UE for doing the RLM.

In this case, the UE may apply the second RLM mode, RLM2 for doing theRLM, such as continuing doing the RLM while it may modify some of theexisting RLM parameters' values as described below.

The UE may use one or any combination of the following rules:

(1) OOS indications being based on X+N evaluation results correspondingto X+N different RSs from the new set, where N is the number of new RLMRS resources;

(2) IS indications being based on Y (Y<X+N) evaluation resultscorresponding to Y different RSs from the new set;

(3) OOS-triggered timer (T310) needing to be extended depending on whenthe RRC reconfiguration is received;

(4) UE prioritizing evaluation of the new RLM RS resource; and

(5) The UE behavior adaptation depending on the type of the new RLM RSresource.

In one embodiment, Y may be increased by at most N when N RLM RSresources are added. In another embodiment, the number Y remainsunchanged (e.g., Y=1) but the IS indications are based on any RLM RSfrom the increased set whichever comes first.

In certain embodiments, the OOS-triggered timer may need to be extendedto accommodate the time for at least M1<N (e.g., M1=1) out-of-syncevaluation periods to allow the evaluation based on one or more newlyadded RLM RSs and/or one or more. This rule may avoid RLF if the new RLMRS resource has a good link quality. In certain embodiments, theOOS-triggered timer may need to be extended to accommodate the time forat least M2 (e.g., M2=N311) in-sync evaluation periods.

In certain embodiments, UE prioritizing evaluation of the new RLM RSresource means that evaluating the new RLM RS resource before evaluatingone, some or all RLM RS resources from the old set.

In certain embodiments, the UE may apply a first behavior (e.g., do notreset timers or counters) if the type of new RLM RS resource is SS/PBCHblock. In certain embodiments, the UE may apply a second behavior (e.g.,reset at least one timer or counter) if the type of new RLM RS resourceis CSI-RS.

In the second scenario of replacing one or more RLM RS resources, theset size does not change. The UE is currently configured with RLM-RS(RLM-RS1), and part of RLM-RS1 is replaced with a new set of RLM-RS(e.g. RLM-RS2) for doing the RLM. The modified RLM-RS 1 is called hereinas RLM-RS1′. The combined set of RLM-RS (RLM-RS4) comprising RLM-RS1′and RLM-RS2 is then used by the UE for doing the RLM.

In this case, the UE may apply the second RLM mode, RLM2 for doing theRLM, for example, continuing doing the RLM while it may modify some ofthe existing RLM parameters' values as described below. According toanother aspect of the second embodiment, if the number of RLM-RS2 islarger than certain threshold (e.g. 4 or more), then the UE may beconfigured to apply the first RLM mode, RLM1. In other words, the UE mayrestart the RLM parameters.

The new RLM RS resource compared to the replaced RLM RS resource mayhave at least one different characteristic. For example, RLM RS type,frequency, RLM RS bandwidth, RLM RS density in time and/or frequency,and RLM RS periodicity, etc.

The UE may use one or any combination of the following rules:

(1) OOS indications being based on the evaluation results based on RLMRS resources from the updated set;

(2) OOS-triggered timer (T310) needing to be extended depending on whenthe RRC reconfiguration is received to accommodate the time for at leastM<N (e.g., M=1) out-of-sync evaluation periods to allow the evaluationbased on one or more newly added RLM RSs;

(3) IS indications being based on Y evaluation results based on RLM RSresources from the updated set;

(4) UE prioritizing evaluations based on the new RLM RS resources; and

(5) The UE behavior adaptation depending on the type of the old and/ornew RLM RS resources.

In certain embodiments, basing on RLM RS resources from the updated setmay mean excluding the replaced RLM RS resources and including thereplacing (new) RLM RS resources.

In certain embodiments, OOS-triggered timer (T310) needing to beextended depending on when the RRC reconfiguration is received may allowto avoid RLF if the new RLM RS resource has a good link quality.

In certain embodiments, UE prioritizing evaluations based on the new RLMRS resources means that evaluating the channel quality for the new RLMRS resources before evaluating one, some or all RSs from the old setexcept for the deleted RLM RS resources.

In certain embodiments, the UE may apply a first behavior if the typehas changed. In certain embodiments, the UE may apply a second behaviorif the type of has not changed.

In the third scenario of one or more RLM RS resources in a number of Lbeing removed, the size of the RLM RS resource set is reduced. The UE iscurrently configured with RLM-RS (RLM-RS1), and part or subset ofRLM-RS1 is removed for doing the RLM. The remaining part of RLM-RS1after removing the removal of the subset of RLM-RS1 is called herein asRLM-RS5. The reduced set of RLM-RS (RLM-RS5) is then used by the UE fordoing the RLM.

In this case, the UE may apply the second RLM mode, RLM2 for doing theRLM, for example, continuing doing the RLM while it may modify some ofthe existing RLM parameters' values as described below. According toanother aspect of this embodiment, if the number of the part of theRLM-RS1 removed is larger than certain threshold (e.g. 4 or more), thenthe UE may be configured to apply the first RLM mode, RLM1. In otherwords, the UE may restart the RLM parameters.

The UE may use one or any combination of the following rules:

(1) OOS indications being based on the evaluation results correspondingto the new (reduced) set of RLM RS resources; and

(2) IS indications being based on evaluation results based on the new(reduced) set.

In certain embodiments, the evaluation results, which are completed ornot, for the removed RS may not be counted into OOS and IS after the UEreceives and applies the new RLM RS configuration.

In the fourth scenario of existing RLM RS resources being fullyreplaced, the existing RLM RS resource (RLM-RS1) is fully replaced withanother new set of the RLM-RS (RLM-RS6), which is then used by the UEfor doing the RLM. In this case, the UE may be configured based onpre-defined rule or based on indication to apply the first RLM mode,RLM1 for doing the RLM. This means that the UE may reset the values ofthe existing parameters which were used for doing RLM based on RLM-RS1.

According to yet another aspect of the rule, the UE may start doing RLMbased on RLM-RS6 after completing one or more ongoing processes relatedto RLM based on RLM-RS1. Examples of the processes are in syncevaluation period, out of sync evaluation period etc.

In another example method performed in a UE, the present disclosuresecondly addresses details about configuration/re-configuration of BLERpair. In the following embodiments, the UE may adapt its RLM procedure,depending on the type of change in BLER pair. In one embodiment, therule whether the UE may trigger RLM1 or RLM2 upon change in BLER pair ornot may be dependent upon the type of re-configuration of the BLER pair.

Each BLER value of the BLER pair is used to map to an SINR or otherquality measurement and generate IS indications and OOS indicationsrespectively. The method assumes that there is a set of BLER pairs thatmay be configured and re-configured by the network based on BLER pairindex 1 comprising BLER IS(1) and BLER OOS(1); BLER pair index 2comprising BLER IS(2) and BLER OOS(2); and so on until BLER pair index Mcomprising BLER IS(M) and BLER OOS(M).

Examples of types of reconfiguration of BLER pair are any change in BLERIS and BLER OOS change; BLER IS increasing and BLER OOS increasing; BLERIS decreasing and BLER OOS decreasing; BLER IS increasing and BLER OOSdecreasing; and BLER IS decreasing and BLER OOS increasing.

In the fifth scenario of increasing in BLER OOS, an increase in BLER OOSindicates that from the moment the UE receives that configuration, itwill tolerate lower SINR values before generating OOS, and it isunderstood that the purpose of the network is to have a moreconservative RLF procedure where the UE does not increase the OOScounters unless the situation is much worse. Hence, upon receiving aconfiguration that increases the BLER OOS, the UE resets the OOScounter(s), such as N310, and stop the RLF related timers, such as T310or T313, if running. In certain embodiments, increasing the BLER OOSmeans increasing the Q_(out) threshold, for example, from 10% to 20%.

In the sixth scenario of decreasing in BLER OOS, a decrease in BLER OOSindicates that from the moment the UE receives that configuration, itmay start generating more OOS for the same SINR values, and it isunderstood that the purpose of the network is to have a lessconservative RLF procedure where the UE may increase the OOS countersfaster. Hence, upon receiving a configuration that decreases the BLEROOS, the UE may reset the OOS counter(s), such as N310, and stop the RLFrelated timers, such as T310 or T313, if running, so that RLF is nottriggered too fast. In certain embodiments, decreasing the BLER OOSmeans decreasing the Q_(out) threshold, for example, from 20% to 10%.

In the seventh scenario of increasing in BLER IS, an increase in BLERIS, i.e. Q_(in) threshold, indicates that from the moment the UEreceives that configuration, it will generate IS indications faster thanwith the previous configuration, so that it may quicker increase thecounters (e.g. N311) that stops the RLF timer (e.g. T311), and it isunderstood that the purpose of the network is to quickly get out of anRLF situation, e.g. when RLF timer is running. In other words, it maytolerate a BLER improvement less significant, e.g. if the increase isfrom 2% to 5%. In other words, the UE starts to generate IS indicationswhen channel statistically starts to have BLER not lower than 5% insteadof not lower than 2% which is more conservative. Hence, upon receiving aconfiguration that increases the BLER IS, the UE resets the IScounter(s), such as N311 or equivalent for secondary cell groups (SCGs),and stop the RLF related timers, e.g. T310, T311 or T313, if running.

In the eighth scenario of decreasing in BLER IS, a decrease in BLER IS,i.e. Q_(in) threshold, indicates that from the moment the UE receivesthat configuration, it will generate IS indications slower, which ismore conservatively than with the previous configuration, so that it mayslower increase the counters (e.g. N311) that stops the RLF timer (e.g.T311), and it is understood that the purpose of the network is to avoidgetting out of an RLF situation too fast, even though the service cannotbe properly provided to the UE, for example, when RLF timer is running.Hence, upon receiving a configuration that decreases the BLER IS, the UEresets the IS counter(s), such as N311 or equivalent for SCGs, and stopthe RLF related timers (e.g. T310, T311 or T313), if running.

The present disclosure further comprises other scenarios which theexample method may be applied to. Combinations of the first, second,and/or third scenarios may also occur one parameter has been changed forone RLM RS resource which is the second scenario, and also one new RLMRS resource was added which is the first scenario, so the combination ofthe corresponding rules may also apply here.

The present disclosure further illustrates UE behavior and RLMperformance requirements during a transition period upon a change in theset of RLM-RS resources. Herein, the UE behavior is described and itsexpected performance during the change, shortly before and shortly afterthe change.

The UE may be required to comply with one or more RLM performancemetrics, even right before the change, during the change, right afterthe change, and any one or more of which may comprise a transitionperiod. In a further embodiment, this requirement may apply, disregardof whether any timer or counter is reset or not. In another embodiment,this requirement may apply only provided a counter like N310 is notreset. In certain embodiments, the one or more RLM performance metricsmay be evaluation period, OOS or IS indication interval, and accuracy ofthe link quality measurement, such as SINR which is then mapped to BLER.

FIG. 8 illustrates an example transition period upon changingconfiguration of RLM-RS resource or the set of RLM-RS resources, inaccordance with certain embodiments. An evaluation period is determinedbased on a sliding window method which is similar to computing a runningaverage, and in the end of each evaluation period, the UE physical layermay indicate OOS to higher layers, which ultimately may lead to RLF.During the transition period, the UE may comply with the most relaxedRLM performance metric (e.g., longest evaluation period) between theperformance metric associated with the old RLM RS configuration and theperformance metric associated with the new RLM RS configuration. Thetransition period may start from the time when the change is applied, orwhen the new configuration is received and last for one most relaxedevaluation period, or the longest RLM-RS periodicity among theconfigured old and new RLM-RS resources. The rule may apply forevaluation period per RLM-RS resource as well as for the evaluationperiod common for all configured RLM-RS resources. In one embodiment,the RLM-RS periodicity during time interval t1 is T1, and the evaluationperiod is a function f(T1), and the UE receives a shorter periodicityT2<T1 for this RLM-RS or even for another RLM-RS resource, which maymake the longest periodicity among all configured RLM-RS resourcesshorter, the new evaluation period becomes a function of f(T2) which issmaller than f(T1), so during the transition time equal tog(max(T1,T2))=g(T1), e.g, g(T1)=f(T1), from the moment when the changeis configured, the UE may indicate to higher layer OOS one or more timebased on the evaluation period f(T1), during which the UE assess thelink quality of the RLM-RS. After the transition period, the evaluationperiod is f(T2).

The present disclosure further discloses an example method implementedin a network node. A network node implements the network side for theembodiments described herein. The network behavior is compliant with theUE embodiments, such configuring RLM parameters, timers, counters, andtriggering RLF at the network side, etc.

For each of the above examples, a set of RLM-RS resources, e.g., LRLM-RS resources, may be either all SSB or all CSI-RS or a combinationof SSB and CSI-RS resources. For the combination case, the rule mayapply to the total group of L RLM-RS resources, or the SSB and CSI-RSresources are treated as separate subgroups and RLM is monitored persubgroup. That is, ISS/OOS indication may be generated per subgroup, orISS/OOS may be generated over total group, even monitoring is done persubgroup. For both the aforementioned cases, any change listed above forthe subgroup affects only the monitoring continuation over the subgroup,where a resource or resources are changed and where all cases listedabove. For example, a UE is configured with L=7 resources out of whichP=3 are SSB and T=4 are CSI-RS based. When one of the CSI-RS resourcesis changed, only monitoring from the group of CSI-RS based RLM-RS isaffected as per information from network or as per predefined rule. TheCSI-RS based group may further be divided into resources that share sameor different configured bandwidth part (BWP), and these subgroups aretreated as described for SSB and CSI-RS subgroups. There may be a rulethat when CSI-RS resource is changed, the monitoring behavior onlychanges within the group of CSI-RS resources configured for the sameBWP. Further, the total group of L SSB or CSI-RS based RLM-RS may bedivided into subgroups based on BWP, such that all resources within oneBWP belong to one group.

In the first embodiment of a method performed in a network node, the UEdeletes measurement, stops timers and resets counters when networkconfigures the UE with a RLM configuration. The first embodimentprovides updates to the 38.331 for some of the embodiments in thepresent disclosure.

In the first embodiment, regarding radio source configuration, the UEshall:

-   -   1> if the received radioResourceConfigDedicated includes the        rlm-Config:        -   2> reconfigure the radio link monitoring parameters as            specified in 5.3.10.x.

In the first embodiment, regarding radio link monitoring parametersreconfiguration, the UE shall:

-   -   1> if the received the rlm-Config contains        ssbResourcesToAddModList;        -   2> for each ssbIndex value included in the            ssbResourcesToAddModList;            -   3> if an entry with the matching ssbIndex exists in the                ssbResourcesToAddModList;                -   4> add a new entry for the received ssbIndex to the                    ssbResourcesToAddModList;    -   1> if the received the rlm-Config contains        csi-RS-ResourcesToAddModList;        -   2> for each csi-rs-Index value included in the            csi-RS-ResourcesToAddModList;            -   3> if an entry with the matching csi-rs-Index exists in                the csi-RS-ResourcesToAddModList;                -   4> add a new entry for the received csi-rs-Index to                    the csi-RS-ResourcesToAddModList;    -   1> if the received the rlm-Config contains        ssbResourcesToRemoveList;        -   2> for each ssbIndex value included in the            ssbResourcesToAddModList;            -   3> remove the entry with the matching ssbIndex from the                ssbResourcesToAddModList;    -   1> if the received the rlm-Config contains        csi-RS-ResourcesToRemoveList;        -   2> for each csi-rs-Index value included in the            csi-RS-ResourcesToRemoveList;            -   3> remove the entry with the matching csi-rs-Index from                the csi-RS-ResourcesToRemoveList;    -   1> if the received the rlm-Config contains        RLM-IS-OOS-threhsoldConfig;        -   2> reconfigure the BLER pair threshold according to the            received index in RLM-IS-OOS-threhsoldConfig, where the            index mapping to the BLER pair is specified in TS 38.211;    -   1> stop the timers T310, T312, T313 and any other RLF related        timer or failure related timer that can be affected by RLM        parameters;    -   1> clear the RLF counters N310, N311, N313, N314 or any other        counter for IS and OOS indications from lower layers that might        be affected by the RLM configuration;    -   1> clear the information included in VarRLF-Report, if any.

In the second embodiment of a method performed in a network node, the UEonly resets RLF related counters and deletes measurements when somespecific RLM re-configuration is performed. For example, the UE resetsRLF related counters only when the BLER pair is provided, wherein theBLER pair is an indication that the UE is being re-configured. Thesecond embodiment provides updates to the 38.331 for some of theembodiments in the present disclosure.

In the second embodiment, regarding radio source configuration, the UEshall:

-   -   1> if the received radioResourceConfigDedicated includes the        rlm-Config:        -   2> reconfigure the radio link monitoring parameters as            specified in 5.3.10.x.

In the second embodiment, regarding radio link monitoring parametersreconfiguration, the UE shall:

-   -   1> if the received the rlm-Config contains        ssbResourcesToAddModList;        -   2> for each ssbIndex value included in the            ssbResourcesToAddModList;            -   3> if an entry with the matching ssbIndex exists in the                ssbResourcesToAddModList;                -   4> add a new entry for the received ssbIndex to the                    ssbResourcesToAddModList;    -   1> if the received the rlm-Config contains        csi-RS-ResourcesToAddModList;        -   2> for each csi-rs-Index value included in the            csi-RS-ResourcesToAddModList;            -   3> if an entry with the matching csi-rs-Index exists in                the csi-RS-ResourcesToAddModList;                -   4> add a new entry for the received csi-rs-Index to                    the csi-RS-ResourcesToAddModList;    -   1> if the received the rlm-Config contains        ssbResourcesToRemoveList;        -   2> for each ssbIndex value included in the            ssbResourcesToAddModList;            -   3> remove the entry with the matching ssbIndex from the                ssbResourcesToAddModList;    -   1> if the received the rlm-Config contains        csi-RS-ResourcesToRemoveList;        -   2> for each csi-rs-Index value included in the            csi-RS-ResourcesToRemoveList;            -   3> remove the entry with the matching csi-rs-Index from                the csi-RS-ResourcesToRemoveList;    -   1> if the received the rlm-Config contains        RLM-IS-OOS-threhsoldConfig;        -   2> reconfigure the BLER pair threshold according to the            received index in RLM-IS-OOS-threhsoldConfig, where the            index mapping to the BLER pair is specified in TS 38.211;        -   2> stop the timers T310, T312, T313 and any other RLF            related timer or failure related timer that can be affected            by RLM parameters;        -   2> clear the RLF counters N310, N311, N313, N314 or any            other counter for IS and OOS indications from lower layers            that might be affected by the RLM configuration;        -   2> clear the information included in VarRLF-Report, if any.

In the third embodiment of a method performed in a network node, the UEonly resets RLF related counters and deletes measurements when somespecific RLM re-configuration is performed. For example, the UE resetsRLF related counters only when any of the RS type resources are beingadded, i.e. the UE does not reset counters or stop timers when RSresources are removed. The third embodiment provides updates to the38.331 for some of the embodiments in the present disclosure.

In the third embodiment, regarding radio source configuration, the UEshall:

-   -   1> if the received radioResourceConfigDedicated includes the        rlm-Config:        -   2> reconfigure the radio link monitoring parameters as            specified in 5.3.10.x.

In the third embodiment, regarding radio link monitoring parametersreconfiguration, the UE shall:

-   -   1> if the received the rlm-Config contains        ssbResourcesToAddModList;        -   2> for each ssbIndex value included in the            ssbResourcesToAddModList;            -   3> if an entry with the matching ssbIndex exists in the                ssbResourcesToAddModList;                -   4> add a new entry for the received ssbIndex to the                    ssbResourcesToAddModList;                -   4> stop the timers T310, T312, T313 and any other                    RLF related timer or failure related timer that can                    be affected by RLM parameters;                -   4> clear the RLF counters N310, N311, N313, N314 or                    any other counter for IS and OOS indications from                    lower layers that might be affected by the RLM                    configuration;                -   4> clear the information included in VarRLF-Report,                    if any;    -   1> if the received the rlm-Config contains        csi-RS-ResourcesToAddModList;        -   2> for each csi-rs-Index value included in the            csi-RS-ResourcesToAddModList;            -   3> if an entry with the matching csi-rs-Index exists in                the csi-RS-ResourcesToAddModList;                -   4> add a new entry for the received csi-rs-Index to                    the csi-RS-ResourcesToAddModList;                -   4> stop the timers T310, T312, T313 and any other                    RLF related timer or failure related timer that can                    be affected by RLM parameters;                -   4> clear the RLF counters N310, N311, N313, N314 or                    any other counter for IS and OOS indications from                    lower layers that might be affected by the RLM                    configuration;                -   4> clear the information included in VarRLF-Report,                    if any;    -   1> if the received the rlm-Config contains        ssbResourcesToRemoveList;        -   2> for each ssbIndex value included in the            ssbResourcesToAddModList;            -   3> remove the entry with the matching ssbIndex from the                ssbResourcesToAddModList;    -   1> if the received the rlm-Config contains        csi-RS-ResourcesToRemoveList;        -   2> for each csi-rs-Index value included in the            csi-RS-ResourcesToRemoveList;            -   3> remove the entry with the matching csi-rs-Index from                the csi-RS-ResourcesToRemoveList;    -   1> if the received the rlm-Config contains        RLM-IS-OOS-threhsoldConfig;        -   2> reconfigure the BLER pair threshold according to the            received index in RLM-IS-OOS-threhsoldConfig, where the            index mapping to the BLER pair is specified in TS 38.211.

In the fourth embodiment of a method performed in a network node, the UEonly resets RLF related counters and deletes measurements when somespecific RLM re-configuration is performed. For example, the UE resetsRLF related counters only when any of the RS type resources are beingremoved, i.e. the UE does not reset counters or stop timers when RSresources are added. The fourth embodiment provides updates to the38.331 for some of the embodiments in the present disclosure.

In the fourth embodiment, regarding radio source configuration, the UEshall:

-   -   1> if the received radioResourceConfigDedicated includes the        rlm-Config:        -   2> reconfigure the radio link monitoring parameters as            specified in 5.3.10.x.

In the fourth embodiment, regarding radio link monitoring parametersreconfiguration, the UE shall:

-   -   1> if the received the rlm-Config contains        ssbResourcesToAddModList;        -   2> for each ssbIndex value included in the            ssbResourcesToAddModList;            -   3> if an entry with the matching ssbIndex exists in the                ssbResourcesToAddModList;                -   4> add a new entry for the received ssbIndex to the                    ssbResourcesToAddModList;                -   4> stop the timers T310, T312, T313 and any other                    RLF related timer or failure related timer that can                    be affected by RLM parameters;                -   4> clear the RLF counters N310, N311, N313, N314 or                    any other counter for IS and OOS indications from                    lower layers that might be affected by the RLM                    configuration;                -   4> clear the information included in VarRLF-Report,                    if any;    -   1> if the received the rlm-Config contains        csi-RS-ResourcesToAddModList;        -   2> for each csi-rs-Index value included in the            csi-RS-ResourcesToAddModList;            -   3> if an entry with the matching csi-rs-Index exists in                the csi-RS-ResourcesToAddModList;                -   4> add a new entry for the received csi-rs-Index to                    the csi-RS-ResourcesToAddModList;    -   1> if the received the rlm-Config contains        ssbResourcesToRemoveList;        -   2> for each ssbIndex value included in the            ssbResourcesToAddModList;            -   3> remove the entry with the matching ssbIndex from the                ssbResourcesToAddModList;            -   3> stop the timers T310, T312, T313 and any other RLF                related timer or failure related timer that can be                affected by RLM parameters;            -   3> clear the RLF counters N310, N311, N313, N314 or any                other counter for IS and OOS indications from lower                layers that might be affected by the RLM configuration;            -   3> clear the information included in VarRLF-Report, if                any;    -   1> if the received the rlm-Config contains        csi-RS-ResourcesToRemoveList;        -   2> for each csi-rs-Index value included in the            csi-RS-ResourcesToRemoveList;            -   3> remove the entry with the matching csi-rs-Index from                the csi-RS-ResourcesToRemoveList;            -   3> stop the timers T310, T312, T313 and any other RLF                related timer or failure related timer that can be                affected by RLM parameters;            -   3> clear the RLF counters N310, N311, N313, N314 or any                other counter for IS and OOS indications from lower                layers that might be affected by the RLM configuration;            -   3> clear the information included in VarRLF-Report, if                any;    -   1> if the received the rlm-Config contains        RLM-IS-OOS-threhsoldConfig;        -   2> reconfigure the BLER pair threshold according to the            received index in RLM-IS-OOS-threhsoldConfig, where the            index mapping to the BLER pair is specified in TS 38.211.

FIG. 9 is an example wireless network, in accordance with certainembodiments. Although the subject matter described herein may beimplemented in any appropriate type of system using any suitablecomponents, the embodiments disclosed herein are described in relationto a wireless network, such as the example wireless network illustratedin FIG. 9. For simplicity, the wireless network of FIG. 9 only depictsnetwork 906, network nodes 960 and 960 b, and wireless devices (WDs)910, 910 b, and 910 c. In practice, a wireless network may furtherinclude any additional elements suitable to support communicationbetween wireless devices or between a wireless device and anothercommunication device, such as a landline telephone, a service provider,or any other network node or end device. Of the illustrated components,network node 960 and wireless device (WD) 910 are depicted withadditional detail. In some embodiments, the network node 960 may be abase station, such as gNB. In certain embodiments, the wireless device910 may be a user equipment, which is further illustrated in FIG. 19.The wireless network may provide communication and other types ofservices to one or more wireless devices to facilitate the wirelessdevices' access to and/or use of the services provided by, or via, thewireless network.

The wireless network may comprise and/or interface with any type ofcommunication, telecommunication, data, cellular, and/or radio networkor other similar type of system. In some embodiments, the wirelessnetwork may be configured to operate according to specific standards orother types of predefined rules or procedures. Thus, particularembodiments of the wireless network may implement communicationstandards, such as Global System for Mobile Communications (GSM),Universal Mobile Telecommunications System (UMTS), Long Term Evolution(LTE), and/or other suitable 2G, 3G, 4G, or 5G standards; wireless localarea network (WLAN) standards, such as the IEEE 802.11 standards; and/orany other appropriate wireless communication standard, such as theWorldwide Interoperability for Microwave Access (WiMax), Bluetooth,Z-Wave and/or ZigBee standards.

Network 906 may comprise one or more backhaul networks, core networks,IP networks, public switched telephone networks (PSTNs), packet datanetworks, optical networks, wide-area networks (WANs), local areanetworks (LANs), wireless local area networks (WLANs), wired networks,wireless networks, metropolitan area networks, and other networks toenable communication between devices.

Network node 960 and WD 910 comprise various components described inmore detail below. These components work together in order to providenetwork node and/or wireless device functionality, such as providingwireless connections in a wireless network. In different embodiments,the wireless network may comprise any number of wired or wirelessnetworks, network nodes, base stations, controllers, wireless devices,relay stations, and/or any other components or systems that mayfacilitate or participate in the communication of data and/or signalswhether via wired or wireless connections.

As used herein, network node refers to equipment capable, configured,arranged and/or operable to communicate directly or indirectly with awireless device and/or with other network nodes or equipment in thewireless network to enable and/or provide wireless access to thewireless device and/or to perform other functions (e.g., administration)in the wireless network. Examples of network nodes include, but are notlimited to, access points (APs) (e.g., radio access points), basestations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs(eNBs) and NR NodeBs (gNBs)). Base stations may be categorized based onthe amount of coverage they provide (or, stated differently, theirtransmit power level) and may then also be referred to as femto basestations, pico base stations, micro base stations, or macro basestations. A base station may be a relay node or a relay donor nodecontrolling a relay. A network node may also include one or more (orall) parts of a distributed radio base station such as centralizeddigital units and/or remote radio units (RRUs), sometimes referred to asRemote Radio Heads (RRHs). Such remote radio units may or may not beintegrated with an antenna as an antenna integrated radio. Parts of adistributed radio base station may also be referred to as nodes in adistributed antenna system (DAS). Yet further examples of network nodesinclude multi-standard radio (MSR) equipment such as MSR BSs, networkcontrollers such as radio network controllers (RNCs) or base stationcontrollers (BSCs), base transceiver stations (BTSs), transmissionpoints, transmission nodes, multi-cell/multicast coordination entities(MCEs), core network nodes (e.g., MSCs, MMEs), O&M nodes, OSS nodes, SONnodes, positioning nodes (e.g., E-SMLCs), and/or MDTs. As anotherexample, a network node may be a virtual network node as described inmore detail below. More generally, however, network nodes may representany suitable device (or group of devices) capable, configured, arranged,and/or operable to enable and/or provide a wireless device with accessto the wireless network or to provide some service to a wireless devicethat has accessed the wireless network.

In FIG. 9, network node 960 includes processing circuitry 970, devicereadable medium 980, interface 990, auxiliary equipment 988, powersource 986, power circuitry 987, and antenna 962. Although network node960 illustrated in the example wireless network of FIG. 9 may representa device that includes the illustrated combination of hardwarecomponents, other embodiments may comprise network nodes with differentcombinations of components. It is to be understood that a network nodecomprises any suitable combination of hardware and/or software needed toperform the tasks, features, functions and methods disclosed herein.Moreover, while the components of network node 960 are depicted assingle boxes located within a larger box, or nested within multipleboxes, in practice, a network node may comprise multiple differentphysical components that make up a single illustrated component (e.g.,device readable medium 980 may comprise multiple separate hard drives aswell as multiple RAM modules).

Similarly, network node 960 may be composed of multiple physicallyseparate components (e.g., a NodeB component and a RNC component, or aBTS component and a BSC component, etc.), which may each have their ownrespective components. In certain scenarios in which network node 960comprises multiple separate components (e.g., BTS and BSC components),one or more of the separate components may be shared among severalnetwork nodes. For example, a single RNC may control multiple NodeBs. Insuch a scenario, each unique NodeB and RNC pair, may in some instancesbe considered a single separate network node. In some embodiments,network node 960 may be configured to support multiple radio accesstechnologies (RATs). In such embodiments, some components may beduplicated (e.g., separate device readable medium 980 for the differentRATs) and some components may be reused (e.g., the same antenna 962 maybe shared by the RATs). Network node 960 may also include multiple setsof the various illustrated components for different wirelesstechnologies integrated into network node 960, such as, for example,GSM, WCDMA, LTE, NR, WiFi, or Bluetooth wireless technologies. Thesewireless technologies may be integrated into the same or different chipor set of chips and other components within network node 960.

Processing circuitry 970 is configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being provided by a network node. These operationsperformed by processing circuitry 970 may include processing informationobtained by processing circuitry 970 by, for example, converting theobtained information into other information, comparing the obtainedinformation or converted information to information stored in thenetwork node, and/or performing one or more operations based on theobtained information or converted information, and as a result of saidprocessing making a determination.

Processing circuitry 970 may comprise a combination of one or more of amicroprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software and/or encoded logicoperable to provide, either alone or in conjunction with other networknode 960 components, such as device readable medium 980, network node960 functionality. For example, processing circuitry 970 may executeinstructions stored in device readable medium 980 or in memory withinprocessing circuitry 970. Such functionality may include providing anyof the various wireless features, functions, or benefits discussedherein. In some embodiments, processing circuitry 970 may include asystem on a chip (SOC).

In some embodiments, processing circuitry 970 may include one or more ofradio frequency (RF) transceiver circuitry 972 and baseband processingcircuitry 974. In some embodiments, radio frequency (RF) transceivercircuitry 972 and baseband processing circuitry 974 may be on separatechips (or sets of chips), boards, or units, such as radio units anddigital units. In alternative embodiments, part or all of RF transceivercircuitry 972 and baseband processing circuitry 974 may be on the samechip or set of chips, boards, or units

In certain embodiments, some or all of the functionality describedherein as being provided by a network node, base station, eNB or othersuch network device may be performed by processing circuitry 970executing instructions stored on device readable medium 980 or memorywithin processing circuitry 970. In alternative embodiments, some or allof the functionality may be provided by processing circuitry 970 withoutexecuting instructions stored on a separate or discrete device readablemedium, such as in a hard-wired manner. In any of those embodiments,whether executing instructions stored on a device readable storagemedium or not, processing circuitry 970 can be configured to perform thedescribed functionality. The benefits provided by such functionality arenot limited to processing circuitry 970 alone or to other components ofnetwork node 960, but are enjoyed by network node 960 as a whole, and/orby end users and the wireless network generally.

Device readable medium 980 may comprise any form of volatile ornon-volatile computer readable memory including, without limitation,persistent storage, solid-state memory, remotely mounted memory,magnetic media, optical media, random access memory (RAM), read-onlymemory (ROM), mass storage media (for example, a hard disk), removablestorage media (for example, a flash drive, a Compact Disk (CD) or aDigital Video Disk (DVD)), and/or any other volatile or non-volatile,non-transitory device readable and/or computer-executable memory devicesthat store information, data, and/or instructions that may be used byprocessing circuitry 970. Device readable medium 980 may store anysuitable instructions, data or information, including a computerprogram, software, an application including one or more of logic, rules,code, tables, etc. and/or other instructions capable of being executedby processing circuitry 970 and, utilized by network node 960. Devicereadable medium 980 may be used to store any calculations made byprocessing circuitry 970 and/or any data received via interface 990. Insome embodiments, processing circuitry 970 and device readable medium980 may be considered to be integrated.

Interface 990 is used in the wired or wireless communication ofsignaling and/or data between network node 960, network 906, and/or WDs910. As illustrated, interface 990 comprises port(s)/terminal(s) 994 tosend and receive data, for example to and from network 906 over a wiredconnection. Interface 990 also includes radio front end circuitry 992that may be coupled to, or in certain embodiments a part of, antenna962. Radio front end circuitry 992 comprises filters 998 and amplifiers996. Radio front end circuitry 992 may be connected to antenna 962 andprocessing circuitry 970. Radio front end circuitry may be configured tocondition signals communicated between antenna 962 and processingcircuitry 970. Radio front end circuitry 992 may receive digital datathat is to be sent out to other network nodes or WDs via a wirelessconnection. Radio front end circuitry 992 may convert the digital datainto a radio signal having the appropriate channel and bandwidthparameters using a combination of filters 998 and/or amplifiers 996. Theradio signal may then be transmitted via antenna 962. Similarly, whenreceiving data, antenna 962 may collect radio signals which are thenconverted into digital data by radio front end circuitry 992. Thedigital data may be passed to processing circuitry 970. In otherembodiments, the interface may comprise different components and/ordifferent combinations of components.

In certain alternative embodiments, network node 960 may not includeseparate radio front end circuitry 992, instead, processing circuitry970 may comprise radio front end circuitry and may be connected toantenna 962 without separate radio front end circuitry 992. Similarly,in some embodiments, all or some of RF transceiver circuitry 972 may beconsidered a part of interface 990. In still other embodiments,interface 990 may include one or more ports or terminals 994, radiofront end circuitry 992, and RF transceiver circuitry 972, as part of aradio unit (not shown), and interface 990 may communicate with basebandprocessing circuitry 974, which is part of a digital unit (not shown).

Antenna 962 may include one or more antennas, or antenna arrays,configured to send and/or receive wireless signals. Antenna 962 may becoupled to radio front end circuitry 990 and may be any type of antennacapable of transmitting and receiving data and/or signals wirelessly. Insome embodiments, antenna 962 may comprise one or more omni-directional,sector or panel antennas operable to transmit/receive radio signalsbetween, for example, 2 GHz and 66 GHz. An omni-directional antenna maybe used to transmit/receive radio signals in any direction, a sectorantenna may be used to transmit/receive radio signals from deviceswithin a particular area, and a panel antenna may be a line of sightantenna used to transmit/receive radio signals in a relatively straightline. In some instances, the use of more than one antenna may bereferred to as MIMO. In certain embodiments, antenna 962 may be separatefrom network node 960 and may be connectable to network node 960 throughan interface or port.

Antenna 962, interface 990, and/or processing circuitry 970 may beconfigured to perform any receiving operations and/or certain obtainingoperations described herein as being performed by a network node. Anyinformation, data and/or signals may be received from a wireless device,another network node and/or any other network equipment. Similarly,antenna 962, interface 990, and/or processing circuitry 970 may beconfigured to perform any transmitting operations described herein asbeing performed by a network node. Any information, data and/or signalsmay be transmitted to a wireless device, another network node and/or anyother network equipment.

Power circuitry 987 may comprise, or be coupled to, power managementcircuitry and is configured to supply the components of network node 960with power for performing the functionality described herein. Powercircuitry 987 may receive power from power source 986. Power source 986and/or power circuitry 987 may be configured to provide power to thevarious components of network node 960 in a form suitable for therespective components (e.g., at a voltage and current level needed foreach respective component). Power source 986 may either be included in,or external to, power circuitry 987 and/or network node 960. Forexample, network node 960 may be connectable to an external power source(e.g., an electricity outlet) via an input circuitry or interface suchas an electrical cable, whereby the external power source supplies powerto power circuitry 987. As a further example, power source 986 maycomprise a source of power in the form of a battery or battery packwhich is connected to, or integrated in, power circuitry 987. Thebattery may provide backup power should the external power source fail.Other types of power sources, such as photovoltaic devices, may also beused.

Alternative embodiments of network node 960 may include additionalcomponents beyond those shown in FIG. 9 that may be responsible forproviding certain aspects of the network node's functionality, includingany of the functionality described herein and/or any functionalitynecessary to support the subject matter described herein. For example,network node 960 may include user interface equipment to allow input ofinformation into network node 960 and to allow output of informationfrom network node 960. This may allow a user to perform diagnostic,maintenance, repair, and other administrative functions for network node960.

As used herein, wireless device (WD) refers to a device capable,configured, arranged and/or operable to communicate wirelessly withnetwork nodes and/or other wireless devices. Unless otherwise noted, theterm WD may be used interchangeably herein with user equipment (UE). Incertain embodiments, the wireless device 910 may be a user equipmentwhich is further depicted in FIGS. 9 and 19. Communicating wirelesslymay involve transmitting and/or receiving wireless signals usingelectromagnetic waves, radio waves, infrared waves, and/or other typesof signals suitable for conveying information through air. In someembodiments, a WD may be configured to transmit and/or receiveinformation without direct human interaction. For instance, a WD may bedesigned to transmit information to a network on a predeterminedschedule, when triggered by an internal or external event, or inresponse to requests from the network. Examples of a WD include, but arenot limited to, a smart phone, a mobile phone, a cell phone, a voiceover IP (VoIP) phone, a wireless local loop phone, a desktop computer, apersonal digital assistant (PDA), a wireless cameras, a gaming consoleor device, a music storage device, a playback appliance, a wearableterminal device, a wireless endpoint, a mobile station, a tablet, alaptop, a laptop-embedded equipment (LEE), a laptop-mounted equipment(LME), a smart device, a wireless customer-premise equipment (CPE). avehicle-mounted wireless terminal device, etc. A WD may supportdevice-to-device (D2D) communication, for example by implementing a 3GPPstandard for sidelink communication, vehicle-to-vehicle (V2V),vehicle-to-infrastructure (V2I), vehicle-to-everything (V2X) and may inthis case be referred to as a D2D communication device. As yet anotherspecific example, in an Internet of Things (IoT) scenario, a WD mayrepresent a machine or other device that performs monitoring and/ormeasurements, and transmits the results of such monitoring and/ormeasurements to another WD and/or a network node. The WD may in thiscase be a machine-to-machine (M2M) device, which may in a 3GPP contextbe referred to as an MTC device. As one particular example, the WD maybe a UE implementing the 3GPP narrow band internet of things (NB-IoT)standard. Particular examples of such machines or devices are sensors,metering devices such as power meters, industrial machinery, or home orpersonal appliances (e.g. refrigerators, televisions, etc.) personalwearables (e.g., watches, fitness trackers, etc.). In other scenarios, aWD may represent a vehicle or other equipment that is capable ofmonitoring and/or reporting on its operational status or other functionsassociated with its operation. A WD as described above may represent theendpoint of a wireless connection, in which case the device may bereferred to as a wireless terminal. Furthermore, a WD as described abovemay be mobile, in which case it may also be referred to as a mobiledevice or a mobile terminal.

As illustrated, wireless device 910 includes antenna 911, interface 914,processing circuitry 920, device readable medium 930, user interfaceequipment 932, auxiliary equipment 934, power source 936 and powercircuitry 937. WD 910 may include multiple sets of one or more of theillustrated components for different wireless technologies supported byWD 910, such as, for example, GSM, WCDMA, LTE, NR, WiFi, WiMAX, orBluetooth wireless technologies, just to mention a few. These wirelesstechnologies may be integrated into the same or different chips or setof chips as other components within WD 910.

Antenna 911 may include one or more antennas or antenna arrays,configured to send and/or receive wireless signals, and is connected tointerface 914. In certain alternative embodiments, antenna 911 may beseparate from WD 910 and be connectable to WD 910 through an interfaceor port. Antenna 911, interface 914, and/or processing circuitry 920 maybe configured to perform any receiving or transmitting operationsdescribed herein as being performed by a WD. Any information, dataand/or signals may be received from a network node and/or another WD. Insome embodiments, radio front end circuitry and/or antenna 911 may beconsidered an interface.

As illustrated, interface 914 comprises radio front end circuitry 912and antenna 911. Radio front end circuitry 912 comprise one or morefilters 918 and amplifiers 916. Radio front end circuitry 914 isconnected to antenna 911 and processing circuitry 920, and is configuredto condition signals communicated between antenna 911 and processingcircuitry 920. Radio front end circuitry 912 may be coupled to or a partof antenna 911. In some embodiments, WD 910 may not include separateradio front end circuitry 912; rather, processing circuitry 920 maycomprise radio front end circuitry and may be connected to antenna 911.Similarly, in some embodiments, some or all of RF transceiver circuitry922 may be considered a part of interface 914. Radio front end circuitry912 may receive digital data that is to be sent out to other networknodes or WDs via a wireless connection. Radio front end circuitry 912may convert the digital data into a radio signal having the appropriatechannel and bandwidth parameters using a combination of filters 918and/or amplifiers 916. The radio signal may then be transmitted viaantenna 911. Similarly, when receiving data, antenna 911 may collectradio signals which are then converted into digital data by radio frontend circuitry 912. The digital data may be passed to processingcircuitry 920. In other embodiments, the interface may comprisedifferent components and/or different combinations of components.

Processing circuitry 920 may comprise a combination of one or more of amicroprocessor, controller, microcontroller, central processing unit,digital signal processor, application-specific integrated circuit, fieldprogrammable gate array, or any other suitable computing device,resource, or combination of hardware, software, and/or encoded logicoperable to provide, either alone or in conjunction with other WD 910components, such as device readable medium 930, WD 910 functionality.Such functionality may include providing any of the various wirelessfeatures or benefits discussed herein. For example, processing circuitry920 may execute instructions stored in device readable medium 930 or inmemory within processing circuitry 920 to provide the functionalitydisclosed herein. In particular embodiments, the processing circuitry920 of the wireless device 910 may perform the method which is furtherillustrated in FIG. 18.

As illustrated, processing circuitry 920 includes one or more of RFtransceiver circuitry 922, baseband processing circuitry 924, andapplication processing circuitry 926. In other embodiments, theprocessing circuitry may comprise different components and/or differentcombinations of components. In certain embodiments processing circuitry920 of WD 910 may comprise a SOC. In some embodiments, RF transceivercircuitry 922, baseband processing circuitry 924, and applicationprocessing circuitry 926 may be on separate chips or sets of chips. Inalternative embodiments, part or all of baseband processing circuitry924 and application processing circuitry 926 may be combined into onechip or set of chips, and RF transceiver circuitry 922 may be on aseparate chip or set of chips. In still alternative embodiments, part orall of RF transceiver circuitry 922 and baseband processing circuitry924 may be on the same chip or set of chips, and application processingcircuitry 926 may be on a separate chip or set of chips. In yet otheralternative embodiments, part or all of RF transceiver circuitry 922,baseband processing circuitry 924, and application processing circuitry926 may be combined in the same chip or set of chips. In someembodiments, RF transceiver circuitry 922 may be a part of interface914. RF transceiver circuitry 922 may condition RF signals forprocessing circuitry 920.

In certain embodiments, some or all of the functionalities describedherein as being performed by a WD may be provided by processingcircuitry 920 executing instructions stored on device readable medium930, which in certain embodiments may be a computer-readable storagemedium. In alternative embodiments, some or all of the functionality maybe provided by processing circuitry 920 without executing instructionsstored on a separate or discrete device readable storage medium, such asin a hard-wired manner. In any of those particular embodiments, whetherexecuting instructions stored on a device readable storage medium ornot, processing circuitry 920 can be configured to perform the describedfunctionality. The benefits provided by such functionality are notlimited to processing circuitry 920 alone or to other components of WD910, but are enjoyed by WD 910 as a whole, and/or by end users and thewireless network generally.

Processing circuitry 920 may be configured to perform any determining,calculating, or similar operations (e.g., certain obtaining operations)described herein as being performed by a WD. These operations, asperformed by processing circuitry 920, may include processinginformation obtained by processing circuitry 920 by, for example,converting the obtained information into other information, comparingthe obtained information or converted information to information storedby WD 910, and/or performing one or more operations based on theobtained information or converted information, and as a result of saidprocessing making a determination.

Device readable medium 930 may be operable to store a computer program,software, an application including one or more of logic, rules, code,tables, etc. and/or other instructions capable of being executed byprocessing circuitry 920. Device readable medium 930 may includecomputer memory (e.g., Random Access Memory (RAM) or Read Only Memory(ROM)), mass storage media (e.g., a hard disk), removable storage media(e.g., a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or anyother volatile or non-volatile, non-transitory device readable and/orcomputer executable memory devices that store information, data, and/orinstructions that may be used by processing circuitry 920. In someembodiments, processing circuitry 920 and device readable medium 930 maybe considered to be integrated.

User interface equipment 932 may provide components that allow for ahuman user to interact with WD 910. Such interaction may be of manyforms, such as visual, audial, tactile, etc. User interface equipment932 may be operable to produce output to the user and to allow the userto provide input to WD 910. The type of interaction may vary dependingon the type of user interface equipment 932 installed in WD 910. Forexample, if WD 910 is a smart phone, the interaction may be via a touchscreen; if WD 910 is a smart meter, the interaction may be through ascreen that provides usage (e.g., the number of gallons used) or aspeaker that provides an audible alert (e.g., if smoke is detected).User interface equipment 932 may include input interfaces, devices andcircuits, and output interfaces, devices and circuits. User interfaceequipment 932 is configured to allow input of information into WD 910,and is connected to processing circuitry 920 to allow processingcircuitry 920 to process the input information. User interface equipment932 may include, for example, a microphone, a proximity or other sensor,keys/buttons, a touch display, one or more cameras, a USB port, or otherinput circuitry. User interface equipment 932 is also configured toallow output of information from WD 910, and to allow processingcircuitry 920 to output information from WD 910. User interfaceequipment 932 may include, for example, a speaker, a display, vibratingcircuitry, a USB port, a headphone interface, or other output circuitry.Using one or more input and output interfaces, devices, and circuits, ofuser interface equipment 932, WD 910 may communicate with end usersand/or the wireless network, and allow them to benefit from thefunctionality described herein.

Auxiliary equipment 934 is operable to provide more specificfunctionality which may not be generally performed by WDs. This maycomprise specialized sensors for doing measurements for variouspurposes, interfaces for additional types of communication such as wiredcommunications etc. The inclusion and type of components of auxiliaryequipment 934 may vary depending on the embodiment and/or scenario.

Power source 936 may, in some embodiments, be in the form of a batteryor battery pack. Other types of power sources, such as an external powersource (e.g., an electricity outlet), photovoltaic devices or powercells, may also be used. WD 910 may further comprise power circuitry 937for delivering power from power source 936 to the various parts of WD910 which need power from power source 936 to carry out anyfunctionality described or indicated herein. Power circuitry 937 may incertain embodiments comprise power management circuitry. Power circuitry937 may additionally or alternatively be operable to receive power froman external power source; in which case WD 910 may be connectable to theexternal power source (such as an electricity outlet) via inputcircuitry or an interface such as an electrical power cable. Powercircuitry 937 may also in certain embodiments be operable to deliverpower from an external power source to power source 936. This may be,for example, for the charging of power source 936. Power circuitry 937may perform any formatting, converting, or other modification to thepower from power source 936 to make the power suitable for therespective components of WD 910 to which power is supplied.

FIG. 10 illustrates one embodiment of a UE in accordance with variousaspects described herein. As used herein, a user equipment or UE may notnecessarily have a user in the sense of a human user who owns and/oroperates the relevant device. Instead, a UE may represent a device thatis intended for sale to, or operation by, a human user but which maynot, or which may not initially, be associated with a specific humanuser (e.g., a smart sprinkler controller). Alternatively, a UE mayrepresent a device that is not intended for sale to, or operation by, anend user but which may be associated with or operated for the benefit ofa user (e.g., a smart power meter). UE 1000 may be any UE identified bythe 3rd Generation Partnership Project (3GPP), including a NB-IoT UE, aMTC UE, and/or an enhanced MTC (eMTC) UE. UE 1000, as illustrated inFIG. 10, is one example of a WD configured for communication inaccordance with one or more communication standards promulgated by the3rd Generation Partnership Project (3GPP), such as 3GPP's GSM, UNITS,LTE, and/or 5G standards. In certain embodiments, the user equipment1000 may be a user equipment which is further depicted in FIG. 19. Asmentioned previously, the term WD and UE may be used interchangeable.Accordingly, although FIG. 10 is a UE, the components discussed hereinare equally applicable to a WD, and vice-versa.

In FIG. 10, UE 1000 includes processing circuitry 1001 that isoperatively coupled to input/output interface 1005, radio frequency (RF)interface 1009, network connection interface 1011, memory 1015 includingrandom access memory (RAM) 1017, read-only memory (ROM) 1019, andstorage medium 1021 or the like, communication subsystem 1031, powersource 1033, and/or any other component, or any combination thereof.Storage medium 1021 includes operating system 1023, application program1025, and data 1027. In other embodiments, storage medium 1021 mayinclude other similar types of information. Certain UEs may utilize allof the components shown in FIG. 10, or only a subset of the components.The level of integration between the components may vary from one UE toanother UE. Further, certain UEs may contain multiple instances of acomponent, such as multiple processors, memories, transceivers,transmitters, receivers, etc.

In FIG. 10, processing circuitry 1001 may be configured to processcomputer instructions and data. Processing circuitry 1001 may beconfigured to implement any sequential state machine operative toexecute machine instructions stored as machine-readable computerprograms in the memory, such as one or more hardware-implemented statemachines (e.g., in discrete logic, FPGA, ASIC, etc.); programmable logictogether with appropriate firmware; one or more stored program,general-purpose processors, such as a microprocessor or Digital SignalProcessor (DSP), together with appropriate software; or any combinationof the above. For example, the processing circuitry 1001 may include twocentral processing units (CPUs). Data may be information in a formsuitable for use by a computer.

In the depicted embodiment, input/output interface 1005 may beconfigured to provide a communication interface to an input device,output device, or input and output device. UE 1000 may be configured touse an output device via input/output interface 1005. An output devicemay use the same type of interface port as an input device. For example,a USB port may be used to provide input to and output from UE 1000. Theoutput device may be a speaker, a sound card, a video card, a display, amonitor, a printer, an actuator, an emitter, a smartcard, another outputdevice, or any combination thereof. UE 1000 may be configured to use aninput device via input/output interface 1005 to allow a user to captureinformation into UE 1000. The input device may include a touch-sensitiveor presence-sensitive display, a camera (e.g., a digital camera, adigital video camera, a web camera, etc.), a microphone, a sensor, amouse, a trackball, a directional pad, a trackpad, a scroll wheel, asmartcard, and the like. The presence-sensitive display may include acapacitive or resistive touch sensor to sense input from a user. Asensor may be, for instance, an accelerometer, a gyroscope, a tiltsensor, a force sensor, a magnetometer, an optical sensor, a proximitysensor, another like sensor, or any combination thereof. For example,the input device may be an accelerometer, a magnetometer, a digitalcamera, a microphone, and an optical sensor.

In FIG. 10, RF interface 1009 may be configured to provide acommunication interface to RF components such as a transmitter, areceiver, and an antenna. Network connection interface 1011 may beconfigured to provide a communication interface to network 1043 a.Network 1043 a may encompass wired and/or wireless networks such as alocal-area network (LAN), a wide-area network (WAN), a computer network,a wireless network, a telecommunications network, another like networkor any combination thereof. For example, network 1043 a may comprise aWi-Fi network. Network connection interface 1011 may be configured toinclude a receiver and a transmitter interface used to communicate withone or more other devices over a communication network according to oneor more communication protocols, such as Ethernet, TCP/IP, SONET, ATM,or the like. Network connection interface 1011 may implement receiverand transmitter functionality appropriate to the communication networklinks (e.g., optical, electrical, and the like). The transmitter andreceiver functions may share circuit components, software or firmware,or alternatively may be implemented separately.

RAM 1017 may be configured to interface via bus 1002 to processingcircuitry 1001 to provide storage or caching of data or computerinstructions during the execution of software programs such as theoperating system, application programs, and device drivers. ROM 1019 maybe configured to provide computer instructions or data to processingcircuitry 1001. For example, ROM 1019 may be configured to storeinvariant low-level system code or data for basic system functions suchas basic input and output (I/O), startup, or reception of keystrokesfrom a keyboard that are stored in a non-volatile memory. Storage medium1021 may be configured to include memory such as RAM, ROM, programmableread-only memory (PROM), erasable programmable read-only memory (EPROM),electrically erasable programmable read-only memory (EEPROM), magneticdisks, optical disks, floppy disks, hard disks, removable cartridges, orflash drives. In one example, storage medium 1021 may be configured toinclude operating system 1023, application program 1025 such as a webbrowser application, a widget or gadget engine or another application,and data file 1027. Storage medium 1021 may store, for use by UE 1000,any of a variety of various operating systems or combinations ofoperating systems.

Storage medium 1021 may be configured to include a number of physicaldrive units, such as redundant array of independent disks (RAID), floppydisk drive, flash memory, USB flash drive, external hard disk drive,thumb drive, pen drive, key drive, high-density digital versatile disc(HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray opticaldisc drive, holographic digital data storage (HDDS) optical disc drive,external mini-dual in-line memory module (DIMM), synchronous dynamicrandom access memory (SDRAM), external micro-DIMM SDRAM, smartcardmemory such as a subscriber identity module or a removable user identity(SIM/RUIM) module, other memory, or any combination thereof. Storagemedium 1021 may allow UE 1000 to access computer-executableinstructions, application programs or the like, stored on transitory ornon-transitory memory media, to off-load data, or to upload data. Anarticle of manufacture, such as one utilizing a communication system maybe tangibly embodied in storage medium 1021, which may comprise a devicereadable medium.

In FIG. 10, processing circuitry 1001 may be configured to communicatewith network 1043 b using communication subsystem 1031. Network 1043 aand network 1043 b may be the same network or networks or differentnetwork or networks. Communication subsystem 1031 may be configured toinclude one or more transceivers used to communicate with network 1043b. For example, communication subsystem 1031 may be configured toinclude one or more transceivers used to communicate with one or moreremote transceivers of another device capable of wireless communicationsuch as another WD, UE, or base station of a radio access network (RAN)according to one or more communication protocols, such as IEEE 802.5,CDMA, WCDMA, GSM, LTE, UTRAN, WiMax, or the like. Each transceiver mayinclude transmitter 1033 and/or receiver 1035 to implement transmitteror receiver functionality, respectively, appropriate to the RAN links(e.g., frequency allocations and the like). Further, transmitter 1033and receiver 1035 of each transceiver may share circuit components,software or firmware, or alternatively may be implemented separately.

In the illustrated embodiment, the communication functions ofcommunication subsystem 1031 may include data communication, voicecommunication, multimedia communication, short-range communications suchas Bluetooth, near-field communication, location-based communicationsuch as the use of the global positioning system (GPS) to determine alocation, another like communication function, or any combinationthereof. For example, communication subsystem 1031 may include cellularcommunication, Wi-Fi communication, Bluetooth communication, and GPScommunication. Network 1043 b may encompass wired and/or wirelessnetworks such as a local-area network (LAN), a wide-area network (WAN),a computer network, a wireless network, a telecommunications network,another like network or any combination thereof. For example, network1043 b may be a cellular network, a Wi-Fi network, and/or a near-fieldnetwork. Power source 1013 may be configured to provide alternatingcurrent (AC) or direct current (DC) power to components of UE 1000.

The features, benefits and/or functions described herein may beimplemented in one of the components of UE 1000 or partitioned acrossmultiple components of UE 1000. Further, the features, benefits, and/orfunctions described herein may be implemented in any combination ofhardware, software or firmware. In one example, communication subsystem1031 may be configured to include any of the components describedherein. Further, processing circuitry 1001 may be configured tocommunicate with any of such components over bus 1002. In anotherexample, any of such components may be represented by programinstructions stored in memory that when executed by processing circuitry1001 perform the corresponding functions described herein. In anotherexample, the functionality of any of such components may be partitionedbetween processing circuitry 1001 and communication subsystem 1031. Inanother example, the non-computationally intensive functions of any ofsuch components may be implemented in software or firmware and thecomputationally intensive functions may be implemented in hardware.

FIG. 11 illustrates an example virtualization environment, according tocertain embodiments. FIG. 11 is a schematic block diagram illustrating avirtualization environment 1100 in which functions implemented by someembodiments may be virtualized. In the present context, virtualizingmeans creating virtual versions of apparatuses or devices which mayinclude virtualizing hardware platforms, storage devices and networkingresources. As used herein, virtualization can be applied to a node(e.g., a virtualized base station or a virtualized radio access node) orto a device (e.g., a UE, a wireless device or any other type ofcommunication device) or components thereof and relates to animplementation in which at least a portion of the functionality isimplemented as one or more virtual components (e.g., via one or moreapplications, components, functions, virtual machines or containersexecuting on one or more physical processing nodes in one or morenetworks).

In some embodiments, some or all of the functions described herein maybe implemented as virtual components executed by one or more virtualmachines implemented in one or more virtual environments 1100 hosted byone or more of hardware nodes 1130. Further, in embodiments in which thevirtual node is not a radio access node or does not require radioconnectivity (e.g., a core network node), then the network node may beentirely virtualized.

The functions may be implemented by one or more applications 1120 (whichmay alternatively be called software instances, virtual appliances,network functions, virtual nodes, virtual network functions, etc.)operative to implement some of the features, functions, and/or benefitsof some of the embodiments disclosed herein. Applications 1120 are runin virtualization environment 1100 which provides hardware 1130comprising processing circuitry 1160 and memory 1190. Memory 1190contains instructions 1195 executable by processing circuitry 1160whereby application 1120 is operative to provide one or more of thefeatures, benefits, and/or functions disclosed herein.

Virtualization environment 1100, comprises general-purpose orspecial-purpose network hardware devices 1130 comprising a set of one ormore processors or processing circuitry 1160, which may be commercialoff-the-shelf (COTS) processors, dedicated Application SpecificIntegrated Circuits (ASICs), or any other type of processing circuitryincluding digital or analog hardware components or special purposeprocessors. Each hardware device may comprise memory 1190-1 which may benon-persistent memory for temporarily storing instructions 1195 orsoftware executed by processing circuitry 1160. Each hardware device maycomprise one or more network interface controllers (NICs) 1170, alsoknown as network interface cards, which include physical networkinterface 1180. Each hardware device may also include non-transitory,persistent, machine-readable storage media 1190-2 having stored thereinsoftware 1195 and/or instructions executable by processing circuitry1160. Software 1195 may include any type of software including softwarefor instantiating one or more virtualization layers 1150 (also referredto as hypervisors), software to execute virtual machines 1140 as well assoftware allowing it to execute functions, features and/or benefitsdescribed in relation with some embodiments described herein.

Virtual machines 1140, comprise virtual processing, virtual memory,virtual networking or interface and virtual storage, and may be run by acorresponding virtualization layer 1150 or hypervisor. Differentembodiments of the instance of virtual appliance 1120 may be implementedon one or more of virtual machines 1140, and the implementations may bemade in different ways.

During operation, processing circuitry 1160 executes software 1195 toinstantiate the hypervisor or virtualization layer 1150, which maysometimes be referred to as a virtual machine monitor (VMM).Virtualization layer 1150 may present a virtual operating platform thatappears like networking hardware to virtual machine 1140.

As shown in FIG. 11, hardware 1130 may be a standalone network node withgeneric or specific components. Hardware 1130 may comprise antenna 11225and may implement some functions via virtualization. Alternatively,hardware 1130 may be part of a larger cluster of hardware (e.g. such asin a data center or customer premise equipment (CPE)) where manyhardware nodes work together and are managed via management andorchestration (MANO) 11100, which, among others, oversees lifecyclemanagement of applications 1120.

Virtualization of the hardware is in some contexts referred to asnetwork function virtualization (NFV). NFV may be used to consolidatemany network equipment types onto industry standard high-volume serverhardware, physical switches, and physical storage, which can be locatedin data centers, and customer premise equipment.

In the context of NFV, virtual machine 1140 may be a softwareimplementation of a physical machine that runs programs as if they wereexecuting on a physical, non-virtualized machine. Each of virtualmachines 1140, and that part of hardware 1130 that executes that virtualmachine, be it hardware dedicated to that virtual machine and/orhardware shared by that virtual machine with others of the virtualmachines 1140, forms a separate virtual network elements (VNE).

Still in the context of NFV, Virtual Network Function (VNF) isresponsible for handling specific network functions that run in one ormore virtual machines 1140 on top of hardware networking infrastructure1130 and corresponds to application 1120 in FIG. 11.

In some embodiments, one or more radio units 11200 that each include oneor more transmitters 11220 and one or more receivers 11210 may becoupled to one or more antennas 11225. Radio units 11200 may communicatedirectly with hardware nodes 1130 via one or more appropriate networkinterfaces and may be used in combination with the virtual components toprovide a virtual node with radio capabilities, such as a radio accessnode or a base station.

In some embodiments, some signaling can be affected with the use ofcontrol system 11230 which may alternatively be used for communicationbetween the hardware nodes 1130 and radio units 11200.

FIG. 12 illustrates an example telecommunication network connected viaan intermediate network to a host computer, according to certainembodiments. With reference to FIG. 12, in accordance with anembodiment, a communication system includes telecommunication network1210, such as a 3GPP-type cellular network, which comprises accessnetwork 1211, such as a radio access network, and core network 1214.Access network 1211 comprises a plurality of base stations 1212 a, 1212b, 1212 c, such as NBs, eNBs, gNBs or other types of wireless accesspoints, each defining a corresponding coverage area 1213 a, 1213 b, 1213c. Each base station 1212 a, 1212 b, 1212 c is connectable to corenetwork 1214 over a wired or wireless connection 1215. A first UE 1291located in coverage area 1213 c is configured to wirelessly connect to,or be paged by, the corresponding base station 1212 c. A second UE 1292in coverage area 1213 a is wirelessly connectable to the correspondingbase station 1212 a. While a plurality of UEs 1291, 1292 are illustratedin this example, the disclosed embodiments are equally applicable to asituation where a sole UE is in the coverage area or where a sole UE isconnecting to the corresponding base station 1212. In certainembodiments, the plurality of UEs 1291, 1292 may be the user equipmentas described with respect to FIG. 19.

Telecommunication network 1210 is itself connected to host computer1230, which may be embodied in the hardware and/or software of astandalone server, a cloud-implemented server, a distributed server oras processing resources in a server farm. Host computer 1230 may beunder the ownership or control of a service provider, or may be operatedby the service provider or on behalf of the service provider.Connections 1221 and 1222 between telecommunication network 1210 andhost computer 1230 may extend directly from core network 1214 to hostcomputer 1230 or may go via an optional intermediate network 1220.Intermediate network 1220 may be one of, or a combination of more thanone of, a public, private or hosted network; intermediate network 1220,if any, may be a backbone network or the Internet; in particular,intermediate network 1220 may comprise two or more sub-networks (notshown).

The communication system of FIG. 12 as a whole enables connectivitybetween the connected UEs 1291, 1292 and host computer 1230. Theconnectivity may be described as an over-the-top (OTT) connection 1250.Host computer 1230 and the connected UEs 1291, 1292 are configured tocommunicate data and/or signaling via OTT connection 1250, using accessnetwork 1211, core network 1214, any intermediate network 1220 andpossible further infrastructure (not shown) as intermediaries. OTTconnection 1250 may be transparent in the sense that the participatingcommunication devices through which OTT connection 1250 passes areunaware of routing of uplink and downlink communications. For example,base station 1212 may not or need not be informed about the past routingof an incoming downlink communication with data originating from hostcomputer 1230 to be forwarded (e.g., handed over) to a connected UE1291. Similarly, base station 1212 need not be aware of the futurerouting of an outgoing uplink communication originating from the UE 1291towards the host computer 1230.

FIG. 13 illustrates an example host computer communicating via a basestation with a user equipment over a partially wireless connection, inaccordance with some embodiments. Example implementations, in accordancewith an embodiment, of the UE, base station and host computer discussedin the preceding paragraphs will now be described with reference to FIG.13. In communication system 1300, host computer 1310 comprises hardware1315 including communication interface 1316 configured to set up andmaintain a wired or wireless connection with an interface of a differentcommunication device of communication system 1300. Host computer 1310further comprises processing circuitry 1318, which may have storageand/or processing capabilities. In particular, processing circuitry 1318may comprise one or more programmable processors, application-specificintegrated circuits, field programmable gate arrays or combinations ofthese (not shown) adapted to execute instructions. Host computer 1310further comprises software 1311, which is stored in or accessible byhost computer 1310 and executable by processing circuitry 1318. Software1311 includes host application 1312. Host application 1312 may beoperable to provide a service to a remote user, such as UE 1330connecting via OTT connection 1350 terminating at UE 1330 and hostcomputer 1310. In providing the service to the remote user, hostapplication 1312 may provide user data which is transmitted using OTTconnection 1350.

Communication system 1300 further includes base station 1320 provided ina telecommunication system and comprising hardware 1325 enabling it tocommunicate with host computer 1310 and with UE 1330. Hardware 1325 mayinclude communication interface 1326 for setting up and maintaining awired or wireless connection with an interface of a differentcommunication device of communication system 1300, as well as radiointerface 1327 for setting up and maintaining at least wirelessconnection 1370 with UE 1330 located in a coverage area (not shown inFIG. 13) served by base station 1320. Communication interface 1326 maybe configured to facilitate connection 1360 to host computer 1310.Connection 1360 may be direct or it may pass through a core network (notshown in FIG. 13) of the telecommunication system and/or through one ormore intermediate networks outside the telecommunication system. In theembodiment shown, hardware 1325 of base station 1320 further includesprocessing circuitry 1328, which may comprise one or more programmableprocessors, application-specific integrated circuits, field programmablegate arrays or combinations of these (not shown) adapted to executeinstructions. Base station 1320 further has software 1321 storedinternally or accessible via an external connection.

Communication system 1300 further includes UE 1330 already referred to.In certain embodiments, the UE 1330 may be the user equipment asdescribed with respect to FIG. 19. Its hardware 1335 may include radiointerface 1337 configured to set up and maintain wireless connection1370 with a base station serving a coverage area in which UE 1330 iscurrently located. Hardware 1335 of UE 1330 further includes processingcircuitry 1338, which may comprise one or more programmable processors,application-specific integrated circuits, field programmable gate arraysor combinations of these (not shown) adapted to execute instructions. UE1330 further comprises software 1331, which is stored in or accessibleby UE 1330 and executable by processing circuitry 1338. Software 1331includes client application 1332. Client application 1332 may beoperable to provide a service to a human or non-human user via UE 1330,with the support of host computer 1310. In host computer 1310, anexecuting host application 1312 may communicate with the executingclient application 1332 via OTT connection 1350 terminating at UE 1330and host computer 1310. In providing the service to the user, clientapplication 1332 may receive request data from host application 1312 andprovide user data in response to the request data. OTT connection 1350may transfer both the request data and the user data. Client application1332 may interact with the user to generate the user data that itprovides.

It is noted that host computer 1310, base station 1320 and UE 1330illustrated in FIG. 13 may be similar or identical to host computer1230, one of base stations 1212 a, 1212 b, 1212 c and one of UEs 1291,1292 of FIG. 12, respectively. This is to say, the inner workings ofthese entities may be as shown in FIG. 13 and independently, thesurrounding network topology may be that of FIG. 12.

In FIG. 13, OTT connection 1350 has been drawn abstractly to illustratethe communication between host computer 1310 and UE 1330 via basestation 1320, without explicit reference to any intermediary devices andthe precise routing of messages via these devices. Networkinfrastructure may determine the routing, which it may be configured tohide from UE 1330 or from the service provider operating host computer1310, or both. While OTT connection 1350 is active, the networkinfrastructure may further take decisions by which it dynamicallychanges the routing (e.g., on the basis of load balancing considerationor reconfiguration of the network).

Wireless connection 1370 between UE 1330 and base station 1320 is inaccordance with the teachings of the embodiments described throughoutthis disclosure. One or more of the various embodiments improve theperformance of OTT services provided to UE 1330 using OTT connection1350, in which wireless connection 1370 forms the last segment. Moreprecisely, the teachings of these embodiments may improve the handlingof redundant data in the transmit buffer and thereby provide benefitssuch as improved efficiency in radio resource use (e.g., nottransmitting redundant data) as well as reduced delay in receiving newdata (e.g., by removing redundant data in the buffer, new data can betransmitted sooner).

A measurement procedure may be provided for the purpose of monitoringdata rate, latency and other factors on which the one or moreembodiments improve. There may further be an optional networkfunctionality for reconfiguring OTT connection 1350 between hostcomputer 1310 and UE 1330, in response to variations in the measurementresults. The measurement procedure and/or the network functionality forreconfiguring OTT connection 1350 may be implemented in software 1311and hardware 1315 of host computer 1310 or in software 1331 and hardware1335 of UE 1330, or both. In embodiments, sensors (not shown) may bedeployed in or in association with communication devices through whichOTT connection 1350 passes; the sensors may participate in themeasurement procedure by supplying values of the monitored quantitiesexemplified above, or supplying values of other physical quantities fromwhich software 1311, 1331 may compute or estimate the monitoredquantities. The reconfiguring of OTT connection 1350 may include messageformat, retransmission settings, preferred routing etc.; thereconfiguring need not affect base station 1320, and it may be unknownor imperceptible to base station 1320. Such procedures andfunctionalities may be known and practiced in the art. In certainembodiments, measurements may involve proprietary UE signalingfacilitating host computer 1310's measurements of throughput,propagation times, latency and the like. The measurements may beimplemented in that software 1311 and 1331 causes messages to betransmitted, in particular empty or ‘dummy’ messages, using OTTconnection 1350 while it monitors propagation times, errors etc.

FIG. 14 illustrates an example method implemented in a communicationsystem including a host computer, a base station and a user equipment,according to certain embodiments in accordance with some embodiments.More specifically, FIG. 14 is a flowchart illustrating a methodimplemented in a communication system, in accordance with oneembodiment. The communication system includes a host computer, a basestation and a UE which may be a user equipment described with referenceto FIG. 19. For simplicity of the present disclosure, only drawingreferences to FIG. 14 will be included in this section. In step 1410,the host computer provides user data. In substep 1411 (which may beoptional) of step 1410, the host computer provides the user data byexecuting a host application. In step 1420, the host computer initiatesa transmission carrying the user data to the UE. In step 1430 (which maybe optional), the base station transmits to the UE the user data whichwas carried in the transmission that the host computer initiated, inaccordance with the teachings of the embodiments described throughoutthis disclosure. In step 1440 (which may also be optional), the UEexecutes a client application associated with the host applicationexecuted by the host computer.

FIG. 15 illustrates an example method implemented in a communicationsystem including a host computer, a base station and a user equipment,in accordance with some embodiments. More specifically, FIG. 15 is aflowchart illustrating a method implemented in a communication system,in accordance with one embodiment. The communication system includes ahost computer, a base station and a UE which may be a user equipmentdescribed with reference to FIG. 19. For simplicity of the presentdisclosure, only drawing references to FIG. 15 will be included in thissection. In step 1510 of the method, the host computer provides userdata. In an optional substep (not shown) the host computer provides theuser data by executing a host application. In step 1520, the hostcomputer initiates a transmission carrying the user data to the UE. Thetransmission may pass via the base station, in accordance with theteachings of the embodiments described throughout this disclosure. Instep 1530 (which may be optional), the UE receives the user data carriedin the transmission.

FIG. 16 illustrates another further example method implemented in acommunication system including a host computer, a base station and auser equipment, in accordance with some embodiments. More specifically,FIG. 16 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be a user equipment described with reference to FIG. 19. Forsimplicity of the present disclosure, only drawing references to FIG. 16will be included in this section. In step 1610 (which may be optional),the UE receives input data provided by the host computer. Additionallyor alternatively, in step 1620, the UE provides user data. In substep1621 (which may be optional) of step 1620, the UE provides the user databy executing a client application. In substep 1611 (which may beoptional) of step 1610, the UE executes a client application whichprovides the user data in reaction to the received input data providedby the host computer. In providing the user data, the executed clientapplication may further consider user input received from the user.Regardless of the specific manner in which the user data was provided,the UE initiates, in substep 1630 (which may be optional), transmissionof the user data to the host computer. In step 1640 of the method, thehost computer receives the user data transmitted from the UE, inaccordance with the teachings of the embodiments described throughoutthis disclosure.

FIG. 17 illustrates another example method implemented in acommunication system including a host computer, a base station and auser equipment, in accordance with some embodiments. More specifically,FIG. 17 is a flowchart illustrating a method implemented in acommunication system, in accordance with one embodiment. Thecommunication system includes a host computer, a base station and a UEwhich may be a user equipment described with reference to FIG. 19. Forsimplicity of the present disclosure, only drawing references to FIG. 17will be included in this section. In step 1710 (which may be optional),in accordance with the teachings of the embodiments described throughoutthis disclosure, the base station receives user data from the UE. Instep 1720 (which may be optional), the base station initiatestransmission of the received user data to the host computer. In step1730 (which may be optional), the host computer receives the user datacarried in the transmission initiated by the base station.

Any appropriate steps, methods, features, functions, or benefitsdisclosed herein may be performed through one or more functional unitsor modules of one or more virtual apparatuses. Each virtual apparatusmay comprise a number of these functional units. These functional unitsmay be implemented via processing circuitry, which may include one ormore microprocessor or microcontrollers, as well as other digitalhardware, which may include digital signal processors (DSPs),special-purpose digital logic, and the like. The processing circuitrymay be configured to execute program code stored in memory, which mayinclude one or several types of memory such as read-only memory (ROM),random-access memory (RAM), cache memory, flash memory devices, opticalstorage devices, etc. Program code stored in memory includes programinstructions for executing one or more telecommunications and/or datacommunications protocols as well as instructions for carrying out one ormore of the techniques described herein. In some implementations, theprocessing circuitry may be used to cause the respective functional unitto perform corresponding functions according one or more embodiments ofthe present disclosure.

FIG. 18 is a flow diagram of another example method performed at a userequipment, in accordance with certain embodiments. Method 1800 begins atstep 1810 with the UE performing a RLM procedure with first RLMparameters.

At step 1820, the method 1800 comprises receiving, from a network node,a message including at least one second RLM parameter. In certainembodiments, the first RLM parameters and the second RLM parameter areRLM reference signal (RLM-RS) resources for in sync and out of syncindications, block error rate (BLER) for in-sync and out-of-syncindications, or a combination of RLM-RS resources and BLER for in-syncand out-of-sync indications.

At step 1830, the method 1800 comprises identifying a difference betweenthe first RLM parameters and the at least one second RLM parameter. Incertain embodiments, the method 1800 may comprise identifying that thefirst RLM parameters are a first group of RLM-RS resources, andidentifying that the at least one second RLM parameter is a second groupof RLM-RS resources added to the first group of RLM-RS resources. Incertain embodiments, the method 1800 may comprise identifying that thefirst RLM parameter is a first group of RLM-RS resources, andidentifying that the at least one second RLM parameter is a second groupof RLM-RS resources that replace a subset of the first group of RLM-RSresources. In certain embodiments, the method 1800 may compriseidentifying that the first RLM parameter is a first group of RLM-RSresources, and identifying that the at least one second RLM parameter isa second group of RLM-RS resources comprising the first group of RLM-RSresources without a subset of RLM-RS resources. In certain embodiments,the method 1800 may comprise identifying that the first RLM parameter isa first group of RLM-RS resources, and identifying that the at least onesecond RLM parameter is a second group of RLM-RS resources which replacethe first group of RLM-RS resources. In certain embodiments, the method1800 may comprise identifying that the at least one second RLM parameterincreases a BLER threshold to generate the out-of-sync indications. Incertain embodiments, the method 1800 may comprise identifying that theat least one second RLM parameter decreases a BLER threshold to generatethe out-of-sync indications. In certain embodiments, the method 1800 maycomprise identifying that the at least one second RLM parameterincreases a BLER threshold to generate the in-sync indications. Incertain embodiments, the method 1800 may comprise identifying that theat least one second RLM parameter decreases a BLER threshold to generatethe in-sync indications.

At step 1840, the method 1800 comprises determining the type of changebetween the first RLM parameters and the second RLM parameter. Incertain embodiments, the method 1800 may comprise determining thatwhether the first group of RLM-RS resources is the same type of RLM-RSresources as the second group of RLM-RS resources or not.

At step 1850, the method 1800 comprises resetting at least one of thefirst RLM parameters in response to identifying the difference betweenthe first RLM parameters and the second RLM parameter. In certainembodiments, the method 1800 may comprise resetting at least oneout-of-sync counter in response to the second RLM parameter increasingor decreasing a BLER threshold to generate the out-of-sync indications.In certain embodiments, the method 1800 may comprise resetting at leastone in-sync counter in response to the second RLM parameter increasingor decreasing a BLER threshold to generate the in-sync indications. Incertain embodiments, the method 1800 may comprise resetting at least onetimer or counter when the first group of RLM-RS resources is the sametype of RLM-RS resources as the second group of RLM-RS resources. Incertain embodiments, the method 1800 may comprise not resetting anytimers or counters when the first group of RLM-RS resources is not thesame type of RLM-RS resources as the second group of RLM-RS resources.

In certain embodiment, the method 1800 may further comprise adapting thefirst group of the RLM-RS resources and the added second group of RLM-RSresources. In certain embodiment, the method 1800 may further compriseadapting the partly-replaced first group of the RLM-RS resources and thereplacing second group of RLM-RS resources. In certain embodiments, themethod 1800 may further comprise adapting the first group of RLM-RSresources without the subset of RLM-RS resources. In certainembodiments, the method 1800 may further comprise adapting the secondgroup of RLM-RS resources. In certain embodiments, the method 1800 mayfurther comprise stopping at least one radio link failure (RLF) relatedtimer.

FIG. 19 is a schematic block diagram of an exemplary user equipment, inaccordance with certain embodiments. The user equipment 1900 may be usedin a wireless network (for example, the wireless network 906 shown inFIG. 9). The user equipment 1900 may be implemented in a wireless device910 shown in FIG. 9. User equipment 1900 is operable to carry out theexample methods described with reference to FIG. 18 and possibly anyother processes or methods disclosed herein. It is also to be understoodthat the method in FIG. 18 is not necessarily carried out solely by userequipment 1900. At least some operations of the method can be performedby one or more other entities.

User equipment 1900 may comprise processing circuitry, which may includeone or more microprocessor or microcontrollers, as well as other digitalhardware, which may include digital signal processors (DSPs),special-purpose digital logic, and the like. In some embodiments, theprocessing circuitry of user equipment 1900 may be the processingcircuitry 920 shown in FIG. 9. In some embodiments, the processingcircuitry of user equipment 1900 may be the processor 1001 shown in FIG.10. The processing circuitry may be configured to execute program codestored in memory 1015 shown in FIG. 10, which may include one or severaltypes of memory such as read-only memory (ROM), random-access memory,cache memory, flash memory devices, optical storage devices, etc.Program code stored in memory includes program instructions forexecuting one or more telecommunications and/or data communicationsprotocols as well as instructions for carrying out one or more of thetechniques described herein, in several embodiments. In someimplementations, the processing circuitry may be used to causeperforming unit 1910, receiving unit 1920, identifying unit 1930,determining unit 1940, and resetting unit 1950, and any other suitableunits of user equipment 1900 to perform corresponding functionsaccording one or more embodiments of the present disclosure, such as atransmitter and a receiver.

As illustrated in FIG. 19, user equipment 1900 includes performing unit1910, receiving unit 1920, identifying unit 1930, determining unit 1940,and resetting unit 1950. The performing unit 1910 may be configured toperform a RLM procedure with first RLM parameters.

The receiving unit 1920 may be configured to receive, from a networknode, a message including at least one second RLM parameter. In certainembodiments, the first RLM parameters and the second RLM parameter areRLM reference signal (RLM-RS) resources for in sync and out of syncindications, block error rate (BLER) for in-sync and out-of-syncindications, or a combination of RLM-RS resources and BLER for in-syncand out-of-sync indications.

The identifying unit 1930 may be configured to identify a differencebetween the first RLM parameters and the at least one second RLMparameter. In certain embodiments, the identifying unit 1930 may beconfigured to identify that the first RLM parameters are a first groupof RLM-RS resources, and to identify that the at least one second RLMparameter is a second group of RLM-RS resources added to the first groupof RLM-RS resources. In certain embodiments, the identifying unit 1930may be configured to identify that the first RLM parameter is a firstgroup of RLM-RS resources, and to identify that the at least one secondRLM parameter is a second group of RLM-RS resources that replace asubset of the first group of RLM-RS resources. In certain embodiments,the identifying unit 1930 may be configured to identify that the firstRLM parameter is a first group of RLM-RS resources, and to identify thatthe at least one second RLM parameter is a second group of RLM-RSresources comprising the first group of RLM-RS resources without asubset of RLM-RS resources. In certain embodiments, the identifying unit1930 may be configured to identify that the first RLM parameter is afirst group of RLM-RS resources, and to identify that the at least onesecond RLM parameter is a second group of RLM-RS resources which replacethe first group of RLM-RS resources. In certain embodiments, theidentifying unit 1930 may be configured to identify that the at leastone second RLM parameter increases a BLER threshold to generate theout-of-sync indications. In certain embodiments, the identifying unit1930 may be configured to identify that the at least one second RLMparameter decreases a BLER threshold to generate the out-of-syncindications. In certain embodiments, the identifying unit 1930 may beconfigured to identify that the at least one second RLM parameterincreases a BLER threshold to generate the in-sync indications. Incertain embodiments, the identifying unit 1930 may be configured toidentify that the at least one second RLM parameter decreases a BLERthreshold to generate the in-sync indications.

The determining unit 1940 may be configured to determine the type ofchange between the first RLM parameters and the second RLM parameter. Incertain embodiments, the determining unit 1940 may be configured todetermine that whether the first group of RLM-RS resources is the sametype of RLM-RS resources as the second group of RLM-RS resources or not.

The resetting unit 1950 may be configured to reset at least one of thefirst RLM parameters in response to identifying the difference betweenthe first RLM parameters and the second RLM parameter. In certainembodiments, the resetting unit 1950 may be configured to reset at leastone out-of-sync counter in response to the second RLM parameterincreasing or decreasing a BLER threshold to generate the out-of-syncindications. In certain embodiments, the resetting unit 1950 may beconfigured to reset at least one in-sync counter in response to thesecond RLM parameter increasing or decreasing a BLER threshold togenerate the in-sync indications. In certain embodiments, the resettingunit 1950 may be configured to reset at least one timer or counter whenthe first group of RLM-RS resources is the same type of RLM-RS resourcesas the second group of RLM-RS resources. In certain embodiments, theresetting unit 1950 may be configured not to reset any timers orcounters when the first group of RLM-RS resources is not the same typeof RLM-RS resources as the second group of RLM-RS resources.

In certain embodiment, the UE 1900 may further be configured to adaptthe first group of the RLM-RS resources and the added second group ofRLM-RS resources. In certain embodiment, the UE 1900 may further beconfigured to adapt the partly-replaced first group of the RLM-RSresources and the replacing second group of RLM-RS resources. In certainembodiments, the UE 1900 may further be configured to adapt the firstgroup of RLM-RS resources without the subset of RLM-RS resources. Incertain embodiments, the UE 1900 may further be configured to adapt thesecond group of RLM-RS resources. In certain embodiments, the UE 1900may further be configured to stop at least one radio link failure (RLF)related timer.

The term unit may have conventional meaning in the field of electronics,electrical devices and/or electronic devices and may include, forexample, electrical and/or electronic circuitry, devices, modules,processors, receivers, transmitters, memories, logic solid state and/ordiscrete devices, computer programs or instructions for carrying outrespective tasks, procedures, computations, outputs, and/or displayingfunctions, and so on, as such as those that are described herein.

According to various embodiments, an advantage of features herein isthat providing a steady and continuous radio link monitoring uponconfiguring the UE by identifying a difference between the current RLMparameters and the future RLM parameters, so that the UE may beconfigured to adapt the future RLM parameters by adapting the differencewhile performing the current RLM parameters.

While processes in the figures may show a particular order of operationsperformed by certain embodiments of the invention, it should beunderstood that such order is exemplary (e.g., alternative embodimentsmay perform the operations in a different order, combine certainoperations, overlap certain operations, etc.).

While the invention has been described in terms of several embodiments,those skilled in the art will recognize that the invention is notlimited to the embodiments described, can be practiced with modificationand alteration within the spirit and scope of the appended claims. Thedescription is thus to be regarded as illustrative instead of limiting.

The invention claimed is:
 1. A method for performing radio linkmonitoring comprising: performing, by a user equipment (UE), a radiolink monitoring (RLM) procedure with first RLM parameters; receiving, atthe UE, a message including at least one second RLM parameter;identifying, by the UE, a difference between the first RLM parametersand the at least one second RLM parameter; and resetting, at the UE, atleast one of the first RLM parameters in response to identifying thedifference between the first RLM parameters and the at least one secondRLM parameter.
 2. The method according to claim 1, wherein the first RLMparameters and the at least one second RLM parameter are RLM referencesignal (RLM-RS) resources for in sync and out of sync indications, blockerror rate (BLER) for in-sync and out-of-sync indications, or acombination of RLM-RS resources and BLER for in-sync and out-of-syncindications.
 3. The method according to claim 2, wherein identifying thedifference between the first RLM parameters and the at least one secondRLM parameter comprises: identifying that the first RLM parameters are afirst group of RLM-RS resources; and identifying that the at least onesecond RLM parameter is a second group of RLM-RS resources added to thefirst group of RLM-RS resources.
 4. The method according to claim 3,further comprising adapting the first group of the RLM-RS resources andthe added second group of RLM-RS resources.
 5. The method according toclaim 3: wherein the first group of RLM-RS resources is not the sametype of RLM-RS resources as the second group of RLM-RS resources, andwherein the UE does not reset any timers or counters.
 6. The methodaccording to claim 3: wherein the first group of RLM-RS resources is thesame type of RLM-RS resources as the second group of RLM-RS resources,and wherein the UE resets at least one timer or counter.
 7. The methodaccording to claim 2, wherein identifying the difference between thefirst RLM parameters and the at least one second RLM parametercomprises: identifying that the first RLM parameters are a first groupof RLM-RS resources; and identifying that the at least one second RLMparameter is a second group of RLM-RS resources that replace a subset ofthe first group of RLM-RS resources.
 8. The method according to claim 7,further comprising adapting the partly-replaced first group of theRLM-RS resources and the replacing second group of RLM-RS resources. 9.The method according to claim 2, wherein identifying the differencebetween the first RLM parameters and the at least one second RLMparameter comprises: identifying that the first RLM parameters are afirst group of RLM-RS resources; and identifying that the at least onesecond RLM parameter is a second group of RLM-RS resources comprisingthe first group of RLM-RS resources without a subset of RLM-RSresources.
 10. The method according to claim 9, further comprisingadapting the first group of RLM-RS resources without the subset ofRLM-RS resources.
 11. The method according to claim 2, whereinidentifying the difference between the first RLM parameters and the atleast one second RLM parameter comprises: identifying that the first RLMparameters are a first group of RLM-RS resources; and identifying thatthe at least one second RLM parameter is a second group of RLM-RSresources which replace the first group of RLM-RS resources.
 12. Themethod according to claim 2, wherein: identifying the difference betweenthe first RLM parameters and the at least one second RLM parametercomprises identifying that the at least one second RLM parameterincreases a BLER threshold to generate the out-of-sync indications; andresetting at least one of the first RLM parameters comprises resettingat least one out-of-sync counter in response to identifying thedifference between the first RLM parameters and the at least one secondRLM parameter.
 13. The method according to claim 2, wherein: identifyingthe difference between the first RLM parameters and the at least onesecond RLM parameter comprises identifying that the at least one secondRLM parameter decreases a BLER threshold to generate the out-of-syncindications, and resetting at least one of the first RLM parameterscomprises resetting at least one out-of-sync counter in response toidentifying the difference between the first RLM parameters and the atleast one second RLM parameter.
 14. The method according to claim 2,wherein: identifying the difference between the first RLM parameters andthe at least one second RLM parameter comprises identifying that the atleast one second RLM parameter increases a BLER threshold to generatethe in-sync indications, and resetting at least one of the first RLMparameters comprises resetting at least one in-sync counter in responseto identifying the difference between the first RLM parameters and theat least one second RLM parameter.
 15. The method according to claim 2,wherein: identifying the difference between the first RLM parameters andthe at least one second RLM parameter comprises identifying that the atleast one second RLM parameter decreases a BLER threshold to generatethe in-sync indications, and resetting at least one of the first RLMparameters comprises resetting at least one in-sync counter in responseto identifying the difference between the first RLM parameters and theat least one second RLM parameter.
 16. A user equipment for performingradio link monitoring, comprising: at least one processor; and at leastone storage that stores processor-executable instructions, when executedby the processor, causes a user equipment to: perform a radio linkmonitoring (RLM) procedure with first RLM parameters; receive, from anetwork node, a message including at least one second RLM parameter;identify a difference between the first RLM parameters and the at leastone second RLM parameter; and reset at least one of the first RLMparameters in response to identifying the difference between the firstRLM parameters and the at least one second RLM parameter.
 17. The userequipment according to claim 16, wherein the first RLM parameters andthe at least one second RLM parameter are RLM reference signal (RLM-RS)resources for in sync and out of sync indications, block error rate(BLER) for in-sync and out-of-sync indications, or a combination ofRLM-RS resources and BLER for in-sync and out-of-sync indications. 18.The user equipment according to claim 17, wherein the UE identifying thedifference between the first RLM parameters and the at least one secondRLM parameter comprises: identifying that the first RLM parameters are afirst group of RLM-RS resources; and identifying that the at least onesecond RLM parameter is a second group of RLM-RS resources added to thefirst group of RLM-RS resources.
 19. The user equipment according toclaim 18: wherein when the first group of RLM-RS resources is not thesame type of RLM-RS resources as the second group of RLM-RS resources,and wherein the UE (1000) does not reset any timers or counters.
 20. Theuser equipment according to claim 18: wherein when the first group ofRLM-RS resources is the same type of RLM-RS resources as the secondgroup of RLM-RS resources, and wherein the UE (1000) resets at least onetimer or counter.
 21. The user equipment according to claim 17, whereinthe UE identifying the difference between the first RLM parameters andthe at least one second RLM parameter comprises: identifying that thefirst RLM parameter is a first group of RLM-RS resources; andidentifying that the at least one second RLM parameter is a second groupof RLM-RS resources that replace a subset of the first group of RLM-RSresources.
 22. The user equipment according to claim 17, wherein the UEidentifying the difference between the first RLM parameters and the atleast one second RLM parameter comprises: identifying that the first RLMparameter is a first group of RLM-RS resources; and identifying that theat least one second RLM parameter is a second group of RLM-RS resourcescomprising the first group of RLM-RS resources without a subset ofRLM-RS resources.
 23. The user equipment according to claim 17, whereinthe UE identifying the difference between the first RLM parameters andthe at least one second RLM parameter comprises: identifying that thefirst RLM parameter is a first group of RLM-RS resources; andidentifying that the at least one second RLM parameter is a second groupof RLM-RS resources which replace the first group of RLM-RS resources.24. The user equipment according to claim 17, wherein: the UEidentifying the difference between the first RLM parameter and the atleast one second RLM parameter comprises identifying that the at leastone second RLM parameter increases a BLER threshold to generate theout-of-sync indications, and the UE resetting at least one of the firstRLM parameters comprises resetting at least one out-of-sync counter inresponse to identifying the difference between the first RLM parametersand the at least one second RLM parameter.
 25. The user equipmentaccording to claim 17, wherein: the UE identifying the differencebetween the first RLM parameters and the at least one second RLMparameter comprises identifying that the at least one second RLMparameter decreases a BLER threshold to generate the out-of-syncindications, and the UE resetting at least one of the first RLMparameters comprises resetting at least one out-of-sync counter inresponse to identifying the difference between the first RLM parametersand the at least one second RLM parameter.
 26. The user equipmentaccording to claim 17, wherein: the UE identifying the differencebetween the first RLM parameters and the at least one second RLMparameter comprises identifying that the at least one second RLMparameter increases a BLER threshold to generate the in-syncindications, and the UE resetting at least one of the first RLMparameters comprises resetting at least one in-sync counter in responseto identifying the difference between the first RLM parameters and theat least one second RLM parameter.
 27. The user equipment according toclaim 11, wherein: the UE identifying the difference between the firstRLM parameters and the at least one second RLM parameter comprisesidentifying that the at least one second RLM parameter decreases a BLERthreshold to generate the in-sync indications, and resetting at leastone of the first RLM parameters comprises resetting at least one in-synccounter in response to identifying the difference between the first RLMparameters and the at least one second RLM parameter.